orkiva Open this resource#
Console route: /persistentvolumes. This is a cluster-scoped resource; no namespace is part of its identity.
- Select the correct cluster in the sidebar.
- Open PersistentVolumes 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#
Phase, StorageClass, capacity, access modes, reclaim policy and bound claim.
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 PVs and follow the claim link to the consuming namespace. Inspect the underlying volume configuration in YAML. The PV page is a resource editor, not a storage-provider backup console.
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#
Before deleting or reassigning a volume, identify the application using its claim and the reclaim policy. Confirm recovery with the storage operator rather than assuming a volume object can be recreated to recover data.
- 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.