Can helm release valuesFrom a configmap partly, thanks.

[johnzheng1975]

Can helm release valuesFrom a configmap partly, thanks.
For some reason (values.yaml is too long, some securer field do not want to expose), can I only get one filed from values.yaml and put it into helmrelease.

Like below:
Here is configmap.

apiVersion: v1
kind: ConfigMap
metadata:
  name: my-values
  namespace: flux-system
data:
    values.yaml: |
      # Your values here
      replicaCount: 2
      image:
        repository: nginx
        tag: stable

Here is helmrelease, works well.

apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: my-application
  namespace: flux-system
spec:
  interval: 5m
  chart:
    spec:
      chart: name-of-the-chart
      version: "1.2.3"
      sourceRef:
        kind: HelmRepository
        name: my-helm-chart-repo
        namespace: flux-system
  valuesFrom:
  - kind: ConfigMap
    name: my-values
    valuesKey: values.yaml

Can I only expose one key from values.yaml, like

  valuesFrom:
  - kind: ConfigMap
    name: my-values
    valuesKey: values.yaml
    subkey: replicaCount

[stefanprodan]

The in-line values are merged with the all the ConfigMaps/Secrets referred, so yes you can split your values between .spec.values and .spec.valuesFrom. Docs here: https://fluxcd.io/flux/components/helm/helmreleases/#values

PS. There is no subkey in the HelmRelease API, Flux knows how to merge all keys.

[johnzheng1975]

Hi @stefanprodan , I know HelmRelease can handle/merge, and also be split between .spec.values and .spec.valuesFrom.
But my requirement is: For some reason (values.yaml is too long, some securer field do not want to expose), can I only get one filed from values.yaml and put it into helmrelease. Somehow it is feature requirement like subkey.
So, helm release do support such requirement, right?

[stefanprodan]

values.yaml is too long, some securer field do not want to expose

Split the values and place only the secret keys in a Kubernetes Secret that is referred in valuesFrom.

[johnzheng1975]

This file is not own by me, and I cannot split it. ^_^.
Ok, I use another way to implement my requirements.
Thanks @stefanprodan