Corentin Néau

## Additional QA ### Problem Adding an RKE2 cluster to a Fleet setup would lead to multiple log messages about the Fleet agent bundle being deployed, although that deployment would...

Can you reproduce this with a newer Rancher version, e.g. 2.11.x? [This](https://fleet.rancher.io/cluster-registration#manager-initiated-registration) may help understand which resources need to be created and when.

Closing this issue in the absence of feedback.

First hypothesis: the Fleet agent's garbage collection, acting on Helm releases missing a bundle deployment, might interfere with drift correction which installs releases, upgrades them and rolls them back. This...

I have tried to reproduce this with Fleet 0.8 and 0.9 installing a Consul (1.3.3) chart, without success. In both cases, the bundle was ready even after jobs were deleted...

Thanks @jhoblitt, that job spec does reproduce the issue. We will need to have a closer look at our bundle diffs feature to check its support for whole resources. I've...

## Additional QA ### Problem Installing a workload which would delete resources would result in the corresponding `GitRepo`'s status being stuck as `Modified`, reporting deleted resources as `Missing` ### Solution...

## Additional QA See [this comment](https://github.com/rancher/fleet/issues/2829#issuecomment-2346053122)

## Additional QA ### Problem When failing to correct drift on a resource (eg. modified ports array on a service), Fleet would leave a `GitRepo` in `Modified` state, with no...

The above warning has been fixed through #3045. Tried to reproduce this issue against Rancher v2.10.0-rc.3 with Fleet v0.11.0, without success: when updating the `GitRepo` to set its `correctDrift` force...