Open zawistowskipiotr opened 2 weeks ago
Have you observed that only for PodDisruptionBudgets or also for other type of resources?
@jannfis Only for PodDisruptionBudgets
Hey 👋 we also observed this issue. To fix it we tried using server-side apply and it did not change the behaviour. Only editing the resource fixed the issue. Argo version
{
"Version": "v2.10.6+d504d2b",
"BuildDate": "2024-04-05T00:27:47Z",
"GitCommit": "d504d2b1d92f0cf831a124a5fd1a96ee29fa7679",
"GitTreeState": "clean",
"GoVersion": "go1.21.3",
"Compiler": "gc",
"Platform": "linux/amd64",
"KustomizeVersion": "v5.2.1 2023-10-19T20:13:51Z",
"HelmVersion": "v3.14.3+gf03cc04",
"KubectlVersion": "v0.26.11",
"JsonnetVersion": "v0.20.0"
}
I had never seen this behaviour previous to 2.10 but we did not test a downgrade to see if it fixes the problem
Edit: We only saw this happening when the diffs were in the matcher labels
Checklist:
argocd version
.Describe the bug
When syncing an application with out of sync status of object PDB and set RespectIgnoreDifferences flag to true - object remains out of sync with status successfully synced.
To Reproduce
Sync application with PDB object with status out of sync and set RespectIgnoreDifferences flag to true.
Expected behavior
PDB object is synced
Screenshots
Version
Logs
None during the operation.