You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes will detect false positives about modified resources, reporting differences inside the status field.
This situation is impossible to remediate (status is normally a subresource and is not part of the deployment specs), which also causes a redeployment loop when drift correction (self-healing) is active.
However, this does not happen for all resources, e.g. deployments, but I experienced when installing a chart that contained CRDs.
Expected Behavior
Changes in status fields are not reported as modified resources.
aruiz14
changed the title
[backport v2.8] Drift detection/correction should omit status fields
[backport v0.9] Drift detection/correction should omit status fields
Jun 21, 2024
Some just-deployed resources will be reported as Modified by Fleet, never reaching a Ready status. The reported diff contains only changes in the status field of the resource, which is not really actionable by Fleet.
Further investigation has shown that 2 conditions must be met in order to reproduce this issue:
The resource spec must explicitly set at least one field to its default value, e.g. preserveUnknownFields: false in CRDs.
The same manifest also specifies a status field, despite having empty values, e.g.:
Fleet Agent should ignores status fields when comparingHelm Rollback operations, used internally by Fleet to correct drift, now obey Fleet's global limit on Helm history, restricting the number of kept history items to 2.
Testing
(See repro steps above)
Create a fleet.yaml which will deploy any resource matching the above criteria, e.g. the longhorn-crd chart:
This is a backport issue for #2521, automatically created via GitHub Actions workflow initiated by @aruiz14
Original issue body:
Is there an existing issue for this?
Current Behavior
Sometimes will detect false positives about modified resources, reporting differences inside the
status
field.This situation is impossible to remediate (
status
is normally a subresource and is not part of the deployment specs), which also causes a redeployment loop when drift correction (self-healing) is active.However, this does not happen for all resources, e.g.
deployments
, but I experienced when installing a chart that contained CRDs.Expected Behavior
Changes in
status
fields are not reported as modified resources.Steps To Reproduce
fleet.yaml
is like:NotReady
, reporting some CRDs were modified, e.g.:Environment
Logs
No response
Anything else?
The text was updated successfully, but these errors were encountered: