BeaverDeck logo
BeaverDeck

Home / BeaverDeck / Docs / Insights Guide / Storage Insights / Released PV

Released PV

BeaverDeck uses this check to identify a specific storage condition that may need operator review.

Permissions: viewing checks requires insights: view. Opening a linked object or logs requires the corresponding resource permission, and the BeaverDeck ServiceAccount must be allowed to read the Kubernetes resources used by the check. Suppressing a finding requires insights: edit and affects all users.
Check typepv-released
Insights sectionStorage Insights
Alert severityWarning after 7 days

When It Reports A Finding

A PersistentVolume remains in Released phase for more than 7 days. Recently released volumes are shown as passing within the cleanup window.

Why This Is A Problem

Released volumes can retain storage allocations and data after their claim is gone, creating cost, capacity, and data-lifecycle risk.

Recommended Response

  1. Review the previous claim, StorageClass, reclaim policy, ownership, and data retention requirements.
  2. Archive or recover required data before cleanup.
  3. Recycle or delete the PV and backing storage through the provider-approved process when it is no longer needed.

Scope And Limitations

A Retain reclaim policy can deliberately leave a PV Released. Never delete storage solely because this check fires; verify data ownership first.

After remediation: refresh Storage Insights and verify the underlying resource or metric. Suppress the finding only when the condition is intentional and its risk is accepted.