Open dan-m8t opened 1 year ago
After some research: Argo CD does not do common helm operations like helm install
or helm upgrade
- but Argo CD does respect hooks (helm and argo hooks) when it is templating and applying manifests. So for Argo CD every sync is like a helm install
and I guess that's why they get deleted but cannot be recreated until the deployments are ready and running. Not sure how to work around here right now.
I just saw that Argo CD 2.9 supports Kustomize patches inside of a Application. As I do not want to touch the base charts I will test this out if it fits my needs and will document here.
Thank you so much for sharing your findings!
Any updates @dan-m8t ? BTW, this sounds related to https://github.com/stackrox/stackrox/issues/2482 for which we now have a workaround in the form of https://github.com/stackrox/stackrox/pull/10300
@dan-m8t Could you solve that issue?
Hello,
right now I am fighting with a test setup for stackrox. I am using a wrapper chart to add some more needed automation. So my Chart.yaml looks like this:
This simply pulls the Helm Chart for the central services and applies it with the value files I told Argo CD to use, this works just fine.
If I do a fullsync (which should do nothing when I didn't change anything in git obviously) the secrets needed for central, scanner and scanner-db just gets deleted:
I do not see any real issue here because in the template for example for scanner-db-password are the following hooks:
Afaik Argo CD respects those Helm Hooks and should NOT delete when they're annotated as mentioned.
According to the Argo CD documentation Helm Hooks are ignored when you mix them with Argo Hooks, so I migrated my Argo Hooks to Helm Hooks - first setup works as expected, but another sync with no changes still deletes the secrets and leaves the application broken :/.
Any hints here?
Thanks