Skip to content

chore: Option to disable sync with replace on API Server level (#21427)#22073

Merged
leoluz merged 2 commits intoargoproj:masterfrom
andrii-korotkov-verkada:21427-option-to-disable-sync-with-replace
Feb 28, 2025
Merged

chore: Option to disable sync with replace on API Server level (#21427)#22073
leoluz merged 2 commits intoargoproj:masterfrom
andrii-korotkov-verkada:21427-option-to-disable-sync-with-replace

Conversation

@andrii-korotkov-verkada
Copy link
Contributor

@andrii-korotkov-verkada andrii-korotkov-verkada commented Feb 28, 2025

Closes #21427

Have a global option to disable sync with replace to prevent usage which can cause mini-crises due to pods going down to min replicas if deployments etc. are getting replaced. If users check the replace option, they'd get an error saying that replace was disabled via configuration. Annotations still override this behavior.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Toolchain Guide
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

…roj#21427)

Closes argoproj#21427

Have a global option to disable sync with replace to prevent usage which can cause mini-crises due to pods going down to min replicas if deployments etc. are getting replaced.
If users check the replace option, they'd get an error saying that replace was disabled via configuration. Annotations still override this behavior.

Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
@bunnyshell
Copy link

bunnyshell bot commented Feb 28, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
@codecov
Copy link

codecov bot commented Feb 28, 2025

Codecov Report

Attention: Patch coverage is 75.00000% with 6 lines in your changes missing coverage. Please review.

Project coverage is 55.83%. Comparing base (edbce2a) to head (08b3623).
Report is 439 commits behind head on master.

Files with missing lines Patch % Lines
cmd/argocd-server/commands/argocd_server.go 0.00% 3 Missing ⚠️
server/application/application.go 85.00% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master   #22073      +/-   ##
==========================================
+ Coverage   53.53%   55.83%   +2.29%     
==========================================
  Files         342      342              
  Lines       57111    57119       +8     
==========================================
+ Hits        30574    31892    +1318     
+ Misses      23946    22594    -1352     
- Partials     2591     2633      +42     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@andrii-korotkov-verkada andrii-korotkov-verkada added the ready-for-review An approver should give a final review and merge the PR label Feb 28, 2025
@github-project-automation github-project-automation bot moved this to Ready for final review in Argo CD Review Feb 28, 2025
Copy link
Collaborator

@leoluz leoluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@leoluz leoluz merged commit 07da3d4 into argoproj:master Feb 28, 2025
33 checks passed
@github-project-automation github-project-automation bot moved this from Ready for final review to Done in Argo CD Review Feb 28, 2025
chzar pushed a commit to chzar/argo-cd that referenced this pull request Mar 3, 2025
kingbj940429 pushed a commit to kingbj940429/argo-cd that referenced this pull request Mar 4, 2025
…roj#21427) (argoproj#22073)

Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
Signed-off-by: kingbj0429 <kingbj0429@lunit.io>
Hapshanko pushed a commit to Hapshanko/argo-cd that referenced this pull request Apr 29, 2025
…roj#21427) (argoproj#22073)

Signed-off-by: Andrii Korotkov <andrii.korotkov@verkada.com>
Signed-off-by: Hapshanko <adamgaming391100@gmail.com>
@dudinea dudinea mentioned this pull request Jan 26, 2026
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-review An approver should give a final review and merge the PR

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

Create a global option to disable a sync with Replace

2 participants