Flux alternative to helm command

[Marquizee]

Good day!

I want to implement Flux alternative to this helm command:
helm upgrade --install example-app oci://harbor.local/helm/common-chart --version v0.1.0 -f dev/values.yaml -f dev/clusterX/values.yaml --namespace example-namespace

I have same chart for hundreds of apps and i want to simplify deployment with fluxcd.

but i cant make it working as expected.
Maybe im fighting wrong way.

In repo with values for chart i want to contain those files:

dev/
-- values.yaml
    clusterX/
    -- values.yaml
    clusterY/
    -- values.yaml
test/
-- values.yaml
    clusterX/
    -- values.yaml
    clusterY/
    -- values.yaml
prod/
-- values.yaml
    clusterX/
    -- values.yaml
    clusterY/
    -- values.yaml

What steps i did:

• installed latest version of flux cli
  curl -s https://fluxcd.io/install.sh | bash
• bootstrapped flux

flux bootstrap git --username=git 
      --url=${FLUX_HTTPS_REPO} 
      --path=clusters/${TARGET_CLUSTER}
      --components-extra=${FLUX_EXTRA_COMPONENTS}
      --registry=${FLUX_REGISTRY}
      --branch=${FLUX_BRANCH} 
      --token-auth=true 

• in flux repo under clusters/${TARGET_CLUSTER} i created directory example with those manifests:

apiVersion: source.toolkit.fluxcd.io/v1
kind: GitRepository
metadata:
  name: example-app-values
  namespace: flux-system
spec:
  interval: 1m0s
  ref:
    branch: dev
  secretRef:
    name: flux-system
  timeout: 60s
  url: https://gitlab.local/example-app-values.git

apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: example-app-values
  namespace: flux-system
spec:
  interval: 1m
  sourceRef:
    kind: GitRepository
    name: example-app-values
    namespace: flux-system
  path: .                  
  targetNamespace: example-namespace         
  prune: true

apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: example-two-release
  namespace: devops-namespace
spec:
  chartRef:
    kind: OCIRepository
    name: common-chart
    namespace: flux-system
  valuesFrom:
    - kind: ConfigMap
      name: example-app-chart-values
      valuesKey: values.yaml # default values
    - kind: ConfigMap
      name: example-app-chart-values
      valuesKey: values.clusterX.yaml # cluster specific values

and i have OCIRepository manifest:

apiVersion: source.toolkit.fluxcd.io/v1
kind: OCIRepository
metadata:
  name: common-chart
  namespace: flux-system
spec:
  insecure: true
  layerSelector:
    mediaType: "application/vnd.cncf.helm.chart.content.v1.tar+gzip" # https://github.com/opencontainers/image-spec/blob/v1.0.2/media-types.md 
    operation: copy 
  provider: generic
  ref:
    tag: v0.1.0 
  secretRef:
    name: oci-cred 
  url: oci://harbor.local/helm/common-chart

in values repo in each env i created this file:

apiVersion: kustomize.config.k8s.io/v1beta1
kind: Kustomization

configMapGenerator:
  - name: example-app-values
    files:
      - values.yaml
      - values.clusterX.yaml=./clusterX/values.yaml
      - values.clusterY.yaml=./clusterY/values.yaml
    options:
      disableNameSuffixHash: true

but this means i will hold in configmap ALL values for all clusters, which i want to isolate

[matheuscscp]

Check this out: https://github.com/fluxcd/source-watcher/?tab=readme-ov-file#example-helm-chart-composition

[stefanprodan]

@Marquizee this is a good alternative to Kustomize overlays. You no longer need to use ConfigMap generators, instead you would just have one ArtifactGenerator per cluster, that merged the values directly in the charts.

[Marquizee]

Thank you very much!
I think this is solution for my situation

[stefanprodan]

See the example repos:

• https://github.com/fluxcd/flux2-kustomize-helm-example
• https://github.com/controlplaneio-fluxcd/d2-fleet

You can use Kustomize overlays and have values per env/cluster.

[Marquizee]

Thank you!
I believe that flux2-kustomize-helm-example is not that good scalable solution.
And this tool d2-fleet requires a different approach to deployment, and I don't think we'll be able to fully implement something like this within our team.