# GKE Persistent Volume Claims on Google Cloud | ZopNight

> Every check ZopNight runs on your GKE Persistent Volume Claims on Google Cloud: 3 in total, across governance and orphaned resources.

Source: https://zop.dev/zopnight/rules/gcp/gke-pvc

---

_Google Cloud · 3 checks_

## GKE Persistent Volume Claims on Google Cloud, checked for you.

ZopNight runs 3 checks on your GKE Persistent Volume Claims in Google Cloud, covering orphaned resources and governance. Workloads are scheduled by namespace.

- 3 — checks
- 2 — categories
- Manual — fixes, spelled out
- Yes — scheduled with its namespace

Free to start. No card. The playground just needs your work email.

## Every check, grouped by what it protects.

Each one opens with why it matters and exactly what to change.

### Orphaned resources

Resources no longer attached to anything that needs them, such as unattached volumes and unassigned IPs.

- [PVC Lost Its Volume](https://zop.dev/zopnight/rules/pvc-lost-its-volume)
- [Unbound PVC](https://zop.dev/zopnight/rules/unbound-pvc)

### Governance

Missing tags and labels that break cost attribution, such as no environment, team or cost-centre value.

- [PVC Has No StorageClass](https://zop.dev/zopnight/rules/pvc-has-no-storageclass)

## Find these on your own GKE Persistent Volume Claims.

Connect a read-only role and ZopNight inventories the GKE Persistent Volume Claims you run, then runs all 3 checks against them.

[object Object]