How to use the generated ConfigMap's suffix?

[gerryfletch]

Following the guide, I am using the Kustomize Controller to load a values.yaml into a ConfigMap from a Git repository, which generates a unique suffix.

Is it possible to get Flux to automatically update the HelmRelease#valuesFrom property to include the generated suffix?

I can of course disable the suffix entirely:

generatorOptions:
 disableNameSuffixHash: true

But since the guide includes it, I wondered if there is a way to automatically update it :)

[stefanprodan]

Is it possible to get Flux to automatically update the HelmRelease#valuesFrom property to include the generated suffix?

Yes that’s what the guide shows you, check out the kustomizeconfig.yaml

[iangregsondev]

@gerryfletch @stefanprodan I can't figure this out :-(

I am also using "disableNameSuffixHash" for it to work.

Am I missing something ? I couldn't get it to us the suffix either. I also checked the guide.

Any ideas ?

[gerryfletch]

I'm afraid I couldn't get it to work, so I stuck with disableNameSuffixHash. Let me know if you get something working!

[iangregsondev]

Here is what I am using in my release

  valuesFrom:
    - kind: ConfigMap
      name: kafka-akhq-values

but without the following in the kustomization.yml then it fails saying can't find configmap

generatorOptions:
  disableNameSuffixHash: true

For clarity, here is my configMapGenerator

configMapGenerator:
  - name: kafka-akhq-values
    files:
      - files/values.yaml

[lancerushing]

I've created an example of using generated configmaps and secrets (with hash suffix) in a flux helmrelease valuesFrom.

https://github.com/lancerushing/flux-helmrelease-with-generated-configmap

There is kustomizeconfig.yaml bit that makes it work: (link)

---
## Let Kustomize know how replace the nameReferences
nameReference:
- kind: ConfigMap
  version: v1
  fieldSpecs:
  - path: spec/valuesFrom/name
    kind: HelmRelease
- kind: Secret
  version: v1
  fieldSpecs:
  - path: spec/valuesFrom/name
    kind: HelmRelease

[stefanprodan]

Starting with Flux 2.7, you no longer have to use kustomize generators to trigger a HelmRelease upgrade. If you label the ConfigMaps/Secrets with reconcile.fluxcd.io/watch: Enabled, helm-controller will automatically run an upgrade when a valuesFrom object changes.

Docs here: https://fluxcd.io/flux/components/helm/helmreleases/#reacting-immediately-to-configuration-dependencies