Resolving Pending State During Cluster Removal with k10multicluster Tool
Challenge
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:
Solution
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.
-
Delete the target cluster resources by its name.
-
Get the finalizer name to be deleted.
Example output:
— apiVersion: dist.kio.kasten.io/v1alpha1 kind: Cluster metadata: creationTimestamp: "2022-04-26T11:02:22Z" deletionGracePeriodseconds: 0 deletionTimestamp: "2022-04-26T11:18:54Z" finalizers: — dist.kio.kasten.io/manual—debootstrap generation: 2 labels: dist.kio.kasten.io/cluster—type: secondary name: secondary—cluster namespace: kasten—io—mc resourceVersion: "3630125" uid: 8eae79ca-0a3e-454e-938e-7ac3c281ba4c
-
Manually remove an object’s finalizers by patching the metadata.finalizers field to null:
More Information
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.