Values: Customizing Chart Deployments
What you'll learn: How to override default chart values to customize Helm deployments without modifying the chart itself.
The Core Idea
Every Helm chart comes with default configuration values defined in a values.yaml file. Think of this like a form with pre-filled answers—the chart works out-of-the-box, but you'll often want to change things like replica counts, resource limits, or image tags to fit your specific needs.
Rather than editing the chart directly, Helm lets you override these defaults in two flexible ways: using custom values files or command-line flags.
Using a Values File
Create your own YAML file with just the values you want to change:
# my-values.yaml
replicaCount: 3
image:
tag: "2.0.1"
service:
type: LoadBalancer
Then apply it during installation:
helm install myapp stable/nginx --values my-values.yaml
You can stack multiple values files—later files override earlier ones:
helm install myapp stable/nginx -f base-values.yaml -f prod-values.yaml
Using Command-Line Flags
For quick, one-off overrides, use --set:
helm install myapp stable/nginx --set replicaCount=5 --set image.tag="2.1.0"
Nest values with dot notation: parent.child=value.
Priority Order
When values conflict, Helm follows this precedence (highest wins):
--setflags-fvalues files (last file wins)- Chart's default
values.yaml
Key Takeaway: Values files and --set flags let you customize chart deployments without touching the original chart, making upgrades clean and configurations reusable across environments.