Loading...
Loading...
This guide provides instructions on how to clean up Veeam Kasten for Kubernetes provisioned PVs that are not deleted, causing orphaned volumes in the GKE k8s 1.28 release. It has been observed on GKE running k8s 1.28, Veeam Kasten for Kubernetes provisioned PVs using in-tree provisioner cannot be deleted via “kubectl delete pvc <pvcname>”, resulting in volume sprawl requiring manual remediation. Restoring from snapshots/backups still functions.
Identification Of Issue This section demonstrates how to check for orphaned volumes in the environment and successfully clean them. Environment GKE k8s 1.28.x Kasten K10 Version : 6.5.2 in-tree provisioned “kubernetes.io/gce-pd” Step 1: Protect workloads using Veeam Kasten for Kubernetes. Verify any Orphaned PVs Run the Policy to take a Snap+Export and capture the result.The following screenshot demonstrates a successful snapshot and export.
Click on a version to see all relevant bugs
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.