NodePool context
Inspect provisioning configuration and resource relationships to understand the capacity patterns your platform defines.
Lumen / Karpenter visibility
Understand the capacity behind your workloads.
Connect workload demand with the provisioning objects and events around it. Lumen brings Karpenter detail into the Kubernetes workspace so capacity questions stay close to the cluster.
01 / In your workflow
Working detail. In the right context.
Node-level detail
Move between node resources and workload views to investigate placement and capacity pressure.
Evidence before action
Review relevant object state and events before changing provisioning or disruption settings.
02 / A considered investigation
Context, evidence, then action.
Karpenter controls provisioning. Lumen provides an investigation workspace; changing capacity policies still needs your normal operational review.
- 01
Find the right context
Start with your existing kubeconfig. Choose the cluster and namespace before investigating a resource.
- 02
Follow the evidence
Connect resource state with related workloads, events and logs. Build a picture of the issue before changing the system.
- 03
Review the next action
Inspect YAML and diffs, confirm the environment and permissions, then apply your team’s normal review and change process.
03 / Team adoption
Evaluate against your own operating model.
Choose a representative non-production environment. Confirm resource visibility and credential boundaries, work through your common investigations and document the behaviours you want your team to standardise.
- Check the installed product and integration versions.
- Agree which actions are appropriate in each environment.
- Capture limitations and escalation paths during evaluation.
A clearer next step
Try Lumen in your own environment.
Choose a release, connect an existing Kubernetes context and work through an investigation your team knows well. Talk to us when you need help with rollout or enterprise adoption.