Assigning Template Variables

When the same value appears many times in a template, capture it once in a variable so you do not repeat the long path everywhere.

You declare a variable with a dollar name and the colon-equals operator. In Helm, $name holds whatever expression sits on the right.

Every template variable is written with a leading dollar sign. That is how Helm tells your variable apart from a field on the dot context.

Once assigned, drop the variable into your YAML like any value. Helm substitutes the captured result wherever you write $name.

Variables shine for long expressions. Save the release name once, then reuse the short variable instead of typing the full path again.

Use colon-equals only to first declare a variable. To change its value later in the same scope, reassign with a plain equals sign.

A variable lives inside the block where you declared it. Define it before an if or range and it stays visible inside that block.

Declare a variable inside an if block and it vanishes once the block ends. Outside that scope, Helm cannot see it at all.

Pick short, descriptive names like $fullName or $port. A clear variable name makes the template far easier for teammates to read.

The dot can change as you enter blocks, but a variable keeps its captured value. That stability is exactly why variables are so useful.

The right side of an assignment can be any expression, even a piped one. Helm runs it once and stores the result in your variable.

You wrote {{ $svc := .Values.service.name }} earlier in the template.

You can now declare variables with :=, reassign with =, read them back via the dollar sign, and respect block scope. Tidy templates ahead! 🎯