-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Server-Side Diff Reports out of sync on "status" key (among other noisy diffs) #17394
Comments
also experience these problems with latest version 2.10.2 |
2.10.4 just installed from 2.9.x, after enabling server side diff and waiting for a bit I had a couple of Apps report OutOfSync status due to a missing |
I'm having the same issue. I'm deploying emqx (mqtt broker) which for some reason likes to use the status field to keep track of the uptime of the nodes, this causes a sync to be triggered every loop. status:
conditions:
- lastTransitionTime: '2024-04-14T12:45:31Z'
message: Cluster is ready
reason: Ready
status: 'True'
type: Ready
- lastTransitionTime: '2024-04-14T12:45:30Z'
message: Cluster is available
reason: Available
status: 'True'
type: Available
- lastTransitionTime: '2024-04-14T12:45:30Z'
message: Core nodes is ready
reason: CoreNodesReady
status: 'True'
type: CoreNodesReady
- lastTransitionTime: '2024-04-14T12:43:38Z'
message: Core nodes progressing
reason: CoreNodesProgressing
status: 'True'
type: CoreNodesProgressing
coreNodes:
- connections: 1
uptime: 65596542
version: 5.6.0
- connections: 1
uptime: 65719858
version: 5.6.0 |
personally, we now completely ignore
|
yah adding those now too but I thought argocd internally already ignored those fields |
Checklist:
argocd version
.Describe the bug
Applications using server-side diff report incorrect diffs. Especially notable with app-of-apps, daemonsets.
To Reproduce
Enable server-side diff
Expected behavior
Don't report diffs on fields that shouldn't be synced
Screenshots
Example: an argoCD Application in an app-of-apps setup changes its status when the application syncs
Daemonsets reporting out of sync when a new node is being added / a pod isn't ready yet
Reporting missing labels, even after syncing
Version
Logs
The text was updated successfully, but these errors were encountered: