Unbound PVC
A pending claim never binds, so every pod that mounts it stays Pending indefinitely, the workload does not fail, it simply never starts.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudKubernetes
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Fix unbound persistent volume claim. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.
- Applies to
- EKS Persistent Volume Claims on AWS, AKS Persistent Volume Claims on Azure, GKE Persistent Volume Claims on Google Cloud
- Category
- Orphaned resources. Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-1740RC-1840RC-1940- Full reference
Related checks
See the orphaned resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.