Providing Values via chartFileRef

[ty-machine]

Per the roadmap git chart sources are a non goal.

Migrate users that are using Helm charts from Git

In deprecating this we also will be losing the the chartFileRef option for providing values.

Values from chart files are only supported for charts from a Git repository.

Some users (like myself) have used git chart sources specifically to enable this despite agreeing that chart repository is a better solution. Many public charts like redis are published with this method for differentiating environments. While it may be messy, It would be possible to include this functionality for chart repository sources as helm does download the tar.

[stefanprodan]

Changing the values.yaml to a different file inside the chart could be a property of the HelmChart template e.g.:

apiVersion: helm.fluxcd.io/v2alpha1
kind: HelmRelease
metadata:
  name: redis
  namespace: cache
spec:
  interval: 10m
  releaseName: redis
  chart:
    name: redis
    sourceRef:
      kind: HelmRepository
      name: stable
    valuesFile: "values-production.yaml" # defaults to values.yaml

One way to achieve this, would be for source-controller to overwrite the values.yaml with the content of the yaml from valuesFile inside the chart tarball.

[monotek]

Would be nice to be able to use a values file outside of the chart tarball, which is in the same directory as the helmrelease file.
Motivation is that with a separate values.yaml file doing manual helm upgrade / install / template / lint would be easier.

At the moment i have to use third party tools like yq to do something like this:

yq r /dir/helmrelease.yaml 'spec.values' | helm template . -f -

[hiddeco]

Would be nice to be able to use a values file outside of the chart tarball, which is in the same directory as the helmrelease file.
Motivation is that with a separate values.yaml file doing manual helm upgrade / install / template / lint would be easier.

We are not going to support this, as the spec.chart is a template for a HelmChart that is created by the helm-controller but actually reconciled by the source-controller (which produces an artifact for it, to be used as the Helm chart for the release). There is thus no relation between the source of the HelmRelease and the chart.sourceRef defined in the above example.