Helm Release Customization
What you'll learn: How to fine-tune Helm releases in Flux by overriding values, using external configuration sources, and applying Kustomize patches after Helm rendering.
The Core Idea
When deploying Helm charts with Flux, you rarely want vanilla defaults. Helm Release Customization gives you three powerful techniques to tailor applications to your environment: directly overriding values, pulling configuration from external sources with valuesFrom, and applying post-rendering transformations using Kustomize patches.
Think of it like ordering a customizable sandwich: you can change ingredients directly (overriding values), add items from a special menu (valuesFrom), or have the chef modify it after assembly (post-rendering).
Override Values Inline
The values field in a HelmRelease lets you override chart defaults directly:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
name: my-app
spec:
values:
replicas: 3
service:
type: LoadBalancer
Using valuesFrom for External Sources
Pull values from ConfigMaps or Secrets to keep configuration modular:
spec:
valuesFrom:
- kind: ConfigMap
name: common-config
- kind: Secret
name: db-credentials
This separates sensitive data and shared configuration from your HelmRelease definitions.
Post-Rendering with Kustomize
Apply Kustomize patches after Helm renders templates but before applying to the cluster:
spec:
postRenderers:
- kustomize:
patchesStrategicMerge:
- apiVersion: apps/v1
kind: Deployment
metadata:
name: my-app
spec:
template:
metadata:
labels:
team: platform
This adds labels, annotations, or modifications that Helm charts don't natively support.
Key Takeaway: Flux Helm Release Customization gives you three layers of control—inline overrides for simple changes, valuesFrom for external configuration, and post-rendering for advanced transformations—making any Helm chart fit your exact requirements.