wmgroot

> @wmgroot Any reason why pointing this PR to the `release-2.4` branch? I think it should point to `master`. Updated. We had this based on the 2.4 release branch to...

I've opened a PR showing a possible implementation path (which needs some work). This is against the old repo, but I'd like to get feedback on the direction before investing...

Appreciate it! Helm 3.2.0 also contains a preventative fix for https://github.com/helm/helm/issues/5595, which is currently affecting users in my clusters.

Thanks for the reply. Yes, I believe those fields in combination would allow me to reference the same directory from multiple Kubernetes namespaces.

+1. We are having to fork this chart to use it when deploying with ArgoCD to avoid committing secrets into Git. Most other charts I've worked with support this use...

> I'm not so sure how to do the same when applications repo get updated I believe this concern should now be addressed with the addition of a RollingSync strategy...

Sounds good. I'll wait to hear back for next steps.

Sounds good. I spent some time looking through the skyscanner solution, and I think it can be implemented as another "RollingSync" update strategy. I believe that should address the current...

"RollingSync" is intended to handle the case you describe, where the AppSet spec is not changing, but changes are still being applied through a values file, git-based helm chart update,...

"RollingSync" is intended to handle the case you describe, where the AppSet spec is not changing, but changes are still being applied through a values file, git-based helm chart update,...