How to delete an RKE2 downstream cluster stuck in removing

This document (000021228) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Rancher 2.7.x

Situation

In this case, the user decided to delete the downstream cluster while it was still building, causing it to stick in removing in the Rancher UI

Resolution

The commands below should be executed on the local cluster where Rancher is installed. It will help identify if the deleted downstream cluster is still in the provisioning process, as it was deleted before the provisioning process was complete.

1. To get the name of the stuck cluster

kubectl get clusters.management.cattle.io

2. To determine if it is in the provisioning process causing it to get stuck

kubectl -n fleet-default get clusters.provisioning.cattle.io

3. If the cluster is in there then delete it with the command below

kubectl -n fleet-default  delete cluster.provisioning.cattle.io littletester

4. If it doesn't get deleted then remove the finalize(s) with the below command

kubectl -n fleet-default edit cluster.provisioning.cattle.io littletester

 finalizers:
  - wrangler.cattle.io/provisioning-cluster-remove

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.