Helm Templates and Go Templating

Overview

Author templates that use values, if/range, and named helpers — then render with helm template to verify output.

Helm uses the Go template language plus Sprig-like functions. Keep logic thin; push complexity into values schema and helpers.

This is a core tutorial in Module 4 · Templates of the REBASH Academy Helm for Kubernetes Engineers series — written for Cloud, DevOps, Platform, and SRE engineers.

Prerequisites

• Working with Helm Charts

Learning Objectives

By the end of this tutorial, you will be able to:

• Use .Values, .Release, .Chart
• Apply pipelines and common functions
• Write if / range
• Define and include named templates

Architecture

This topic’s control points and relationships are shown below.

Theory

What it is

Helm templates are Go templates plus a rich function library (Sprig-style helpers such as default, quote, toYaml, and nindent). Files under templates/ mix YAML structure with actions delimited by double braces. At render time Helm evaluates those actions against a root context (often written as a lone dot) that exposes objects such as .Values, .Release, and .Chart.

Core objects you will use constantly:

Object	Typical fields	Role
.Values	Your config tree	User-facing knobs
.Release	Name, Namespace, Service	Instance identity
.Chart	Name, Version, AppVersion	Package metadata
.Files	chart file helpers	Embed non-template files
.Capabilities	API versions	Gate resources by cluster APIs

Why it matters

Templates are where parameterisation becomes real manifests. Weak templates produce silent misconfigurations (wrong labels, missing quotes, nil pointer panics) that only appear at deploy time. Strong templates stay thin: prefer clear values schemas and named helpers over deep nested logic. Reviewers should be able to predict output from values alone.

How it works

Helm walks template files, executes actions, and emits YAML documents separated by ---. Pipelines pass values through functions left to right. Conditionals (if / else) and loops (range) control optional blocks and repeated items. Named templates in _helpers.tpl are defined with define and reused with include — the usual place for standard labels and fully qualified names.

Example shape (not a full chart):

metadata:
  name: {{ include "mychart.fullname" . }}
  labels:
    {{- include "mychart.labels" . | nindent 4 }}
data:
  APP_ENV: {{ .Values.appEnv | quote }}

Always render locally with helm template (and lint) before installing. Whitespace-control dashes on template delimiters matter — stray newlines can break YAML indentation.

Key concepts and comparisons

• Pipelines compose functions: default, required, toYaml, nindent, quote.
• include vs template: include returns a string you can pipeline (preferred for helpers); template writes directly.
• Logic budget: if you need complex branching for every environment, push more into values files or split charts — do not build a programming language inside YAML.

Common pitfalls

• Forgetting to quote values that become labels or annotation strings.
• Dereferencing a missing key (nil pointer evaluating interface…) — use default or dig-style patterns carefully.
• Incorrect nindent levels after toYaml, producing invalid YAML.
• Putting executable business logic in templates that belongs in the application or in values schema validation.

Hands-on Lab

Create a workspace for this tutorial.

mkdir -p ~/rebash-helm/module-04 && cd ~/rebash-helm/module-04

Focus: Edit templates safely and render with helm template

Step 1 – Customise a ConfigMap template

kubectl create namespace rebash-helm
helm create tmpl-demo
python3 - <<'PY'
from pathlib import Path
Path('tmpl-demo/templates/configmap.yaml').write_text('''apiVersion: v1
kind: ConfigMap
metadata:
  name: {{ include "tmpl-demo.fullname" . }}-config
  labels:
    {{- include "tmpl-demo.labels" . | nindent 4 }}
data:
  APP_ENV: {{ .Values.env | default "lab" | quote }}
''')
print(Path('tmpl-demo/templates/configmap.yaml').read_text())
PY

Step 2 – Lint, template, and install

helm lint tmpl-demo
helm template demo ./tmpl-demo -n rebash-helm --set env=lab | grep -A5 'kind: ConfigMap'
helm upgrade --install demo ./tmpl-demo -n rebash-helm --set env=lab
kubectl -n rebash-helm get configmap

Final step – Cleanup note

helm uninstall demo -n rebash-helm --ignore-not-found || true
kubectl delete namespace rebash-helm --ignore-not-found
# Workspace kept for notes; remove with: rm -rf "$(pwd)" when finished

Validation

• Lab commands run under ~/rebash-helm/module-04/
• You can explain each Theory section in your own words
• You used modern tooling where it applies to this topic
• You can describe one production failure mode for this topic

Code Walkthrough

Production practice for Helm Templates and Go Templating always combines:

1. Inspect before you change (status, plan, logs, dry-run)
2. Prefer reversible, documented changes (Git, IaC, drop-ins, version pins)
3. Capture evidence (command output, pipeline logs) for handovers
4. Prefer current tools and APIs over legacy shortcuts
5. Least privilege — escalate credentials only when required

Keep runbooks short enough to follow under pressure. Automate checks; keep humans for judgement.

Security Considerations

• Treat credentials and tokens for helm as privileged — never commit them
• Prefer short-lived auth (OIDC, roles, SSO) over long-lived keys
• Validate blast radius before apply/deploy/delete operations
• Restrict who can approve production changes
• Collect audit logs; limit who can read sensitive traces

Common Mistakes

Forgetting to quote values that become labels or annotation strings.

Validate assumptions against the Theory section and official docs before changing production.

Dereferencing a missing key (nil pointer evaluating interface…) — use default or dig

Lab shortcuts (open security groups, admin roles, skip approvals) must not ship unchanged.

Changing production without a rollback path

Always know how to revert (previous artefact, prior release, state rollback, DNS failback).

Best Practices

• Encode Helm Templates and Go Templating changes as code and review them in pull requests
• Pin versions (images, modules, actions, provider plugins)
• Separate environments with clear promotion gates
• Alert on symptoms with runbooks attached
• Destroy lab resources; tag everything with owner and expiry where possible

Troubleshooting

Symptom	Likely cause	Fix
Auth / permission denied	Wrong identity, policy, or scope	Check caller identity, roles, and least-privilege policies
Timeout / no route	Network, DNS, security group, or endpoint	Trace path, DNS, and allow-lists before retrying
Drift / unexpected plan	Manual change or wrong state/workspace	Reconcile desired vs actual; avoid click-ops on managed resources
Pipeline/job red	Flaky step, cache, or missing secret	Read failing step logs; bisect recent workflow/config changes
Cost spike	Idle load balancer, NAT, oversized compute	Inventory billable resources; stop/delete labs promptly

Summary

Helm Templates and Go Templating is essential for Cloud and DevOps engineers working with helm. Practise the lab until the inspection and change path is muscle memory, then continue the track.

Interview Questions

1. What engine does Helm use for templates?
2. Why use include with helpers instead of duplicating labels?
3. How do required and default functions improve chart safety?
4. What dangers exist with | safe / unescaped HTML-like injection into manifests?
5. How do you debug a failing template render?

Sample answer — question 2

Helpers keep names and labels consistent across templates, which Services and selectors rely on. Duplication invites subtle mismatches that break traffic.

Sample answer — question 4

Careless sprig usage or piping untrusted values into YAML can break structure or inject unexpected fields. Validate inputs, quote carefully, and render in CI before apply.

Related Tutorials

• Course overview
• Helm Values and Overrides

References

• Chart template guide