Loading...
Loading...
This article helps in finding and deleting long-running finalizers that are waiting on other resources and can cause deletions to appear stuck in the terminating state. Description: When Kubernetes attempts to delete the cluster object that has finalizers “dist.kio.kasten.io/debootstrap or dist.kio.kasten.io/manual-debootstrap” specified, the Kubernetes API marks the object for deletion by populating .metadata.deletionTimestamp, and returns a 202-status code (HTTP "Accepted"). The cluster object remains in a terminating/Pending state while the control plane, or other components, take the actions defined by the finalizers. Long-running finalizers that are waiting on other resources can cause deletions to appear stuck in the terminating state. This is a result of the ServiceAccount (or its corresponding token/bindings) being deleted on the secondary cluster, and 401 or 500 error shown in the Veeam Kasten for Kubernetes dashboard. Observation: The Veeam Kasten for Kubernetes multi-cluster dashboard displays ‘Removal Pending’ for primary and secondary clusters, as shown below:
The traditional way to resolve this involves determining which API service is not responding and then debugging that issue. An alternative workaround for this issue is to remove the clusters by manually deleting the finalizers which are restricting deletion of the cluster. Here are the steps to remove an object’s finalizers: List down the target cluster.
The following command can be used to delete all clusters at once:
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.