Skip to content
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

PodDisruptionBudget not syncing with RespectIgnoreDifferences flag #18232

Open
3 tasks done
zawistowskipiotr opened this issue May 15, 2024 · 4 comments
Open
3 tasks done
Labels
bug Something isn't working component:core Syncing, diffing, cluster state cache

Comments

@zawistowskipiotr
Copy link

zawistowskipiotr commented May 15, 2024

Checklist:

  • I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
  • I've included steps to reproduce the bug.
  • I've pasted the output of 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

Zrzut ekranu 2024-05-15 133425
Zrzut ekranu 2024-05-15 133556

Version

argocd: v2.11.0+d3f33c0
  BuildDate: 2024-05-07T16:01:41Z
  GitCommit: d3f33c00197e7f1d16f2a73ce1aeced464b07175
  GitTreeState: clean
  GoVersion: go1.21.9
  Compiler: gc
  Platform: linux/amd64

Logs

None during the operation.

@zawistowskipiotr zawistowskipiotr added the bug Something isn't working label May 15, 2024
@jannfis
Copy link
Member

jannfis commented May 15, 2024

Have you observed that only for PodDisruptionBudgets or also for other type of resources?

@jannfis jannfis added the component:core Syncing, diffing, cluster state cache label May 15, 2024
@zawistowskipiotr
Copy link
Author

@jannfis Only for PodDisruptionBudgets

@joaosilva15
Copy link

joaosilva15 commented May 16, 2024

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

@diablo39
Copy link

diablo39 commented Jun 5, 2024

hello, I have similar issue with PDB object, I'm also using v2.11.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component:core Syncing, diffing, cluster state cache
Projects
None yet
Development

No branches or pull requests

4 participants