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

magda-io / magda

A federated, open-source data catalog for all your big data and small data

https://magda.io

Apache License 2.0

496 stars 93 forks source link

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

Closed t83714 closed 10 months ago

t83714 commented 10 months ago

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 commented 10 months ago

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: https://github.com/magda-io/magda/pull/3483

magda-io / magda

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

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

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