Lifecycle resources
Follow Certificate and related issuer resources to understand status and configuration.
Lumen / cert-manager visibility
Bring certificate lifecycle into view.
Certificates sit across resource relationships, issuer configuration and workload dependencies. Explore the Kubernetes objects behind TLS issues within your working cluster context.
01 / In your workflow
Working detail. In the right context.
Connected investigation
Look at associated resources and events when renewal or issuance needs attention.
Controlled access
Use credentials scoped to the resources you need. Treat certificate and Secret access as a separate permission decision.
02 / A considered investigation
Context, evidence, then action.
cert-manager manages issuance and renewal. Views depend on installed resource versions and your Kubernetes permissions.
- 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.