Closed Cr4mble closed 1 month ago
Thank you for your contribution, but there is already a PR for this: #239. We also have other pending work that is built on top of it, so I'd rather keep that.
Would you be able to test that to help move the PR along?
@itay-grudev Sure, i'm happy to help. Will test your branch in the next days with different scenarios. Thanks !
Our setup includes ArgoCD and SealedSecrets. As in the current helm chart the cloud credentials need to be in plaintext we can't commit this to git (GitOps). That's why we adjusted the helm chart to accept an existing secret that we deployed earlier with ArgoCD and SealedSecrets. We are currently using this for AWS s3 and the backup is working as expected.
We tried to adjust the helm chart as less as possible.
This PR should fix #197