Flux doesn't pick up changes if values in the yaml file changes ?

[jdeokar95]

Hi,
I am using flux cd with helm charts (with Helm Repository) for my deployments. I have a chart which has multiple yaml files which can defines the values to be used to render a chart. However if I change just one of the values in yaml file (which should trigger a deployment eg: image tag) and push my chart to the Helm Repository, flux doesn't trigger a new deployment. It pulls the new chart but doesn't really apply those changes. Please let me know if I am missing something ?

TIA

HelmRelease.yaml
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: my-test-chart
  namespace: flux-system
spec:
  install:
    remediation:
      retries: 3
  upgrade:
    remediation:
      retries: 3
  test:
    enable: true
  interval: 1m0s
  chart:
    spec:
      version: "0.2.2"
      chart:   my-test-chart
      sourceRef:
        kind: HelmRepository
        name:  my-test-chart
      valuesFiles:
        - values.yaml
        - qa.yaml
        - image-version.yaml

[stefanprodan]

Every change to the chart content must be accompanied by a version bump, charts are supposed to be immutable. To configure Flux to automatically upgrade to newer versions set version: 0.2.x.

[jdeokar95]

That explains.. thanks for the clarification

[hiddeco]

There is a PR in the works in fluxcd/source-controller#308 which eventually will make it possible trigger a build for commits instead of version changes in the Chart.yaml.

[jdeokar95]

@hiddeco Thanks for the info.. Looks like it is a feature for git/bucket sources but not for helm repository..

Is there another way where we can change the values outside of the chart ? I see kustomize can be used to create configmaps which changes every time the underlying file change. Does that also require version bump ?

[hiddeco]

That would work without bumping versions.