Every GitOps setup meets the same moment: something is on fire, someone runs kubectl scale on prod, and the fix works. What happens next depends on two settings most people never look at. I ran all three cases in a lab on Rancher 2.15.1 with Fleet (biased, I work at SUSE): three EKS clusters, one app from Git. 1. Self-healing on (correctDrift) I scaled a Deployment from 3 to 1. Fleet put it back to 3 in under 7 seconds. The GitRepo flickered NotReady for about 3 seconds, so no...