I0823 07:50:48.127261 1 machine_controller.go:357] "Skipping deletion of Kubernetes Node associated with Machine as it is not allowed" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/cluster1-control-plane-c97s8" namespace="default" name="cluster1-control-plane-c97s8" reconcileID="13584802-471c-4917-ba93-5326e39cfded" RKE2ControlPlane="default/cluster1-control-plane" Cluster="default/cluster1" Node="cluster1-control-plane-c97s8" cause="cluster is being deleted"
I0823 07:50:48.131652 1 machine_controller.go:452] "Waiting for infrastructure to be deleted" controller="machine" controllerGroup="cluster.x-k8s.io" controllerKind="Machine" Machine="default/cluster1-control-plane-c97s8" namespace="default" name="cluster1-control-plane-c97s8" reconcileID="13584802-471c-4917-ba93-5326e39cfded" RKE2ControlPlane="default/cluster1-control-plane" Cluster="default/cluster1" DockerMachine="default/cluster1-control-plane-xsjlr"
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
Rancher - v2.9.0
Turtles - v0.9.0
CAPD - v1.7.3
Anything else you would like to add?
On turtles v0.10.0, CAPD version was v1.4.3 so creating cluster using workaround and CAPD v1.3.3, deletion was working fine.
(Please transfer to the respective repo, if not a turtles issue)
What steps did you take and what happened?
Steps:
Status:
Logs:
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
Rancher - v2.9.0 Turtles - v0.9.0 CAPD - v1.7.3
Anything else you would like to add?
On turtles v0.10.0, CAPD version was v1.4.3 so creating cluster using workaround and CAPD v1.3.3, deletion was working fine.
(Please transfer to the respective repo, if not a turtles issue)