-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Drift correction not working #2436
Comments
Probably related to #2551 |
I've reproduced the problem with rancher 2.9.1 / 0.10.1 as well: The fleet-agent logs on the cluster are the same messages repeated over and over again. E.g.:
|
I have tried, and failed, to reproduce this against the current In any case, #2917 should reduce the noise compared to logs shared above. |
Is there an existing issue for this?
Current Behavior
If an object is changed, Fleet detects the diff but does nothing to converge to a healthy state.
Expected Behavior
When
spec.correctDrift.enabled=true
, I expect Fleet to try and apply changes as soon as there is a diff.Steps To Reproduce
Have Rancher v2.8.1 installed.
In Rancher, click "Continuous Delivery" and "Git Repos" and select the "fleet-local" workspace.
Add a GitRepo that applies some resource. Make sure to check "Enable Self-Healing" to set
spec.correctDrift.enabled=true
in the bundle.Wait for the GitRepo to sync and become healthy, with the new resource created and in state "Ready".
Edit the resource using
kubectl edit
, e.g. delete a label or something.Observe new state "Modified" for the resource:
Environment
Logs
No response
Anything else?
It looks like #1594 tried to implement drift correction, but it's clearly not working.
The text was updated successfully, but these errors were encountered: