R&D: Helm: Support declarative definition of values files in Git separate from the helm repo

Scenario

I would like to use values.yaml file from Git with a Helm Chart from a Helm Repository not necessarily managed by me ( example the Red Hat Helm Repo ).

https://github.com/argoproj/argo-cd/issues/2789

https://github.com/argoproj/argo-cd/issues/5826 

Problem Statement

When the values-file gets updated, ArgoCD synchronizes the environment using the Helm chart + this values files.

Further steps:

• Go upstream to discuss this, and try to find out possible designs that everybody can agree to

Acceptance Criteria

1. User creates an Application CR which references a Helm Chart and a values.yaml stored in Git.
2. Application is sync'd successfully and workloads are deployed.
3. User changes the referenced values.yaml in Git.
4. Application is re-sync'd and the workloads are updated with the modified values.yaml in Git

Workarounds:

• Create a new helm chart on Git and refer to the 'real' one as a dependency
• Create an Application CR on Git and have values.yaml embedded in it. ( this isn't too bad, but ties users to using the Application CR )

We need to have a better first class support for this since we aim to have first class Helm and GitOps experiences on OpenShift, individually. The workarounds aren't intuitive and give an impression of a broken experience.

Customers

...