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

docs: unset finalizer before deleting an app non-cascadingly #10949

Merged
merged 7 commits into from Mar 6, 2023

Conversation

beyondbill
Copy link
Contributor

@beyondbill beyondbill commented Oct 14, 2022

Signed-off-by: Bo Huang beyondbill@users.noreply.github.com

Our organization sets the finalizer from the default ArgoCD application template. Therefore it is risky to assume that ArgoCD applications always start without the finalizer unless set by argocd app delete with --cascade, as the current docs indicate. It actually caused a P1 incident when one of our SREs followed the instruction in the docs to delete all ArgoCD applications "non-cascadingly" by running kubectl delete app, only to find all staging and prod services deleted! It's preferable to always unset the finalizer before a non-cascade deletion unless the operator knows with certainty that the finalizer has never been set before.

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

  • (c) this does not need to be in the release notes.
  • The title of the PR states what changed
  • 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.
  • Optional. My organization is added to USERS.md.
  • 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).

@codecov
Copy link

codecov bot commented Oct 14, 2022

Codecov Report

Base: 47.71% // Head: 47.71% // No change to project coverage 👍

Coverage data is based on head (acd37f6) compared to base (338245e).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #10949   +/-   ##
=======================================
  Coverage   47.71%   47.71%           
=======================================
  Files         246      246           
  Lines       41908    41908           
=======================================
  Hits        19996    19996           
  Misses      19914    19914           
  Partials     1998     1998           
Impacted Files Coverage Δ
util/settings/settings.go 49.36% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

@crenshaw-dev crenshaw-dev added cherry-pick/2.4 Candidate for cherry picking into the 2.4 release branch cherry-pick/2.5 cherry-pick/2.6 labels Feb 6, 2023
@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.6

@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.5

@crenshaw-dev
Copy link
Collaborator

/cherry-pick release-2.4

@crenshaw-dev crenshaw-dev enabled auto-merge (squash) March 6, 2023 17:37
@crenshaw-dev crenshaw-dev merged commit 152a930 into argoproj:master Mar 6, 2023
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Mar 6, 2023
Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Mar 6, 2023
Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
gcp-cherry-pick-bot bot pushed a commit that referenced this pull request Mar 6, 2023
Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
crenshaw-dev added a commit that referenced this pull request Mar 6, 2023
…#12733)

Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
crenshaw-dev added a commit that referenced this pull request Mar 6, 2023
…#12734)

Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
crenshaw-dev added a commit that referenced this pull request Mar 6, 2023
…#12735)

Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
yyzxw pushed a commit to yyzxw/argo-cd that referenced this pull request Aug 9, 2023
…j#10949)

Signed-off-by: Bo Huang <beyondbill@users.noreply.github.com>
Co-authored-by: Michael Crenshaw <350466+crenshaw-dev@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cherry-pick/2.4 Candidate for cherry picking into the 2.4 release branch cherry-pick/2.5 cherry-pick/2.6
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants