cluster-fleet-default-<clustername>-<id> not wiped on cluster destroy

[hproegel]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Hello,

I am currently working with Rancher to have some automatic things done around it. I am using fleet + bundles + bundledeployments in my environment. As I am using lots of automation to create and destroy clusters on demand I came accross the issue, that on a destroy of the cluster
there are some artifacts remaining on the Rancher Cluster

especially bundle(s) and bundledeployments

I am wondering if this is intentionally not cleaned up or I have to do this manually myself.

I had 100th of objects in my cluster and some of the fleet things didn't behave properly as many of the bundles where pointing to abandoned clusters which from my pov slowed down processes quite a lot.

Thanks & Best regards,
Heinz

Expected Behavior

bundle(s) and bundledeployments are removed from Rancher on a cluster destroy action

Steps To Reproduce

1. create an application bundle and apply it to a target cluster - Group of Clusters - through tagging the cluster/cluster group
2. destroy the cluster
3. observe the artifacts on the Rancher Cluster "Bundle" and "BundleDeployment"

Environment

- Architecture: amd64
- Fleet Version: 0.11.2
- Cluster: 
  - Provider: RKE2
  - Options: 3
  - Kubernetes Version: v1.31.3+rke2r1

Logs

Anything else?

No response