Override on the CLI with --set

Use a dot to walk into the values tree. Here image.tag targets the tag nested under image.

Separate multiple overrides with commas, or repeat the flag. Both forms feed the same values map.

For an array, put the index in square brackets. This writes to the first item of the ingress.hosts list.

Dots and commas inside a value have meaning to Helm. Escape them with a backslash so they stay part of the string.

Numbers and booleans get typed automatically. Use --set-string when you need a value like a version kept as text.

For a large or secret value, --set-file reads the content from a file instead of typing it inline.

Because it is one line, --set shines in scripts and CI where injecting a build number or tag must be quick.

For many or deeply nested overrides, long --set strings get unreadable. That is your cue to switch to a values file.

Any key you pass with --set replaces the chart's default for that key. Untouched keys keep their original values.

Use --set for quick inline overrides with dotted paths, --set-string to keep text, and a values file once it grows. ✅