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

When using cloudSQL DB setup, db-main-account-secret might be incorrectly removed during the initial deployment #3481

Closed
t83714 opened this issue Aug 30, 2023 · 1 comment
Assignees
Labels

Comments

@t83714
Copy link
Contributor

t83714 commented Aug 30, 2023

When using cloudSQL DB setup, db-main-account-secret might be incorrectly removed by helm chart logic during the initial deployment

  • Seems only happen with cloudSQL DB setup and using manually supplied db-main-account-secret secret
  • Seems only happen to the initial deployment
  • 2nd deployment might work (i.e. without getting db-main-account-secret removed)
@t83714 t83714 added the bug label Aug 30, 2023
@t83714 t83714 self-assigned this Aug 30, 2023
t83714 added a commit that referenced this issue Sep 2, 2023
- For #3481, recommend users adding `"helm.sh/resource-policy": keep` annotation on the manual supplied secret.
@t83714
Copy link
Contributor Author

t83714 commented Sep 2, 2023

Couldn't reproduce the problem.
Will add note in helm chart (magda-core) doc to recommend users adding "helm.sh/resource-policy": keep annotation on the manual supplied secret instead.
See PR: #3483

@t83714 t83714 closed this as completed Sep 2, 2023
t83714 added a commit that referenced this issue Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

1 participant