orkiva Open this resource#
Console route: /secrets. This is a namespaced resource; choose the namespace before making a change.
- Select the correct cluster in the sidebar.
- Open Secrets and narrow the list using the available namespace/search controls.
- Select the exact object by name. Verify its scope and identity at the top of the detail page.
For screenshots of the shared list, detail and creation controls, see the resource actions visual guide. Available actions depend on the resource and your permissions.
What to inspect#
Secret type, data keys, size and resource version.
Refresh the resource when you need the latest observation. Overview fields summarize the object; YAML exposes the complete returned document. A placeholder or missing status field should not be read as a successful or zero-valued result.
Use the available features#
Open Secrets only with the appropriate authorization. Review the Data tab and reveal/inspect content only when needed for the task. Use YAML for a permitted edit and keep the type/key structure required by its consumer. Related, Events and History provide context.
Describe, Clone, YAML editing and Delete are shared resource actions where the page and your permissions allow them. Read Create, edit, clone and delete resources before applying a change.
A practical investigation#
Do not share rendered secret values in screenshots, logs or support messages. A Kubernetes Secret is not encrypted merely because its manifest uses base64. Verify the consuming workload after intentional credential rotation.
- Establish the current state and the symptom you want to resolve.
- Identify whether a controller, Helm release or Delivery project owns the object.
- Make the smallest authorized change through that owner when possible.
- Refresh and verify the resulting resource state. Inspect related objects rather than stopping at a successful save message.