CAPI cluster not getting deleted after fleet repo deletion

cpinjani commented 2 weeks ago

What steps did you take and what happened?

Note: In case of v1 cluster, the issue is not occurring and cluster gets deleted. Need to check if we support this scenario for v3.

Steps:

Install turtles/UI extension and import CAPI cluster using fleet & namespace label
Corresponding v3 cluster gets created in Rancher
Disable CAPI Auto-import on namespace from UI or remove auto-import label on namespace from back-end
Remove fleet repo and check CAPI cluster deletion status

$ kubectl get cluster
NAME       PHASE      AGE   VERSION
cluster1   Deleting   63m

logs.tar.gz

What did you expect to happen?

CAPI cluster should get deleted after fleet repo deletion

How to reproduce it?

Steps mentioned above.

Rancher Turtles version

v0.9.0

Anything else you would like to add?

No response

Label(s) to be applied

/kind bug

Danil-Grigorev commented 1 week ago

Disable CAPI Auto-import on namespace from UI or remove auto-import label on namespace from back-end

From that point forward I think turtles should not be responsible for the "import" functionality.

furkatgofurov7 commented 5 days ago

After the team meeting discussion, we agreed that this is the edge case and we need a note to highlight it in maintenance page of turtles book. I will create a separate issue for that in docs repo, so closing it.

rancher / turtles