50 Helm Chart Development Interview Questions (2027)
50 Helm chart interview questions on writing charts: Chart.yaml, values design, _helpers.tpl, template functions, values.schema.json, hooks and tests.
Helm chart interview questions test whether you can write a chart, not just install one: laying out templates, designing values.yaml, writing named templates in _helpers.tpl, using Go template functions safely, validating values with a JSON schema, managing dependencies and testing the rendered output. These 50 questions are written around code you should be able to produce on a whiteboard.
If you need Helm basics (what a release is, how to install and roll back), start with our 70+ Helm interview questions. For production troubleshooting, see Helm scenario-based questions for experienced engineers. Both are listed in our DevOps interview hub. Commands and behaviour were checked against helm.sh for Helm 4 (current release line 4.3) in November 2026.
Key takeaways
- Chart authoring rounds usually include a live task: "template this Deployment so replicas, image and resources come from values."
- Know the files:
Chart.yaml,values.yaml,values.schema.json,templates/,templates/_helpers.tpl,templates/NOTES.txt,charts/andcrds/. - Use
includeplusnindentfor named templates,toYamlfor blocks of values, andrequiredfor mandatory settings. - Chart API
v2is the stable format. Chart APIv3is experimental in Helm 4 and needsHELM_EXPERIMENTAL_CHART_V3=1. - Test with
helm lint,helm template, a schema, andhelm testhooks, and run them in CI.
Question map
| Level | Questions | Typical task |
|---|---|---|
| Freshers | 1 to 15 | Read and explain a small chart; change a value |
| 2 to 5 years | 16 to 38 | Write templates, helpers, schemas and dependencies |
| Senior | 39 to 44 | Design charts for many teams and long-term change |
| Authoring scenarios | 45 to 50 | Fix a broken or badly designed chart |
Freshers: reading a chart
1. What does helm create mychart generate?
A starter chart with Chart.yaml, values.yaml, .helmignore, a charts/ folder and templates for a Deployment, Service, ServiceAccount, Ingress, HPA, _helpers.tpl, NOTES.txt and a test pod. It is a good base, but trim what you do not need.
2. What are the required fields in Chart.yaml?
apiVersion (v2 for Helm 3 and 4 charts), name and version. Common optional fields are appVersion, description, type, dependencies, kubeVersion and maintainers.
3. What must version look like?
A SemVer 2 version such as 1.4.2. Bump it whenever the chart changes; appVersion tracks the application and is informational.
4. What is the difference between application and library chart types?
Application charts render resources and can be installed. Library charts only provide named templates for other charts and cannot be installed on their own.
5. How does a template read a value?
Through the .Values object: {{ .Values.image.repository }}. Values come from values.yaml, parent charts, -f files and --set, with later sources taking priority.
6. What other built-in objects can templates use?
.Release (Name, Namespace, Revision, IsInstall, IsUpgrade), .Chart (fields from Chart.yaml), .Capabilities (cluster and API versions), .Template (current file) and .Files (non-template files in the chart).
7. Why do templates start with {{- sometimes?
The dash trims whitespace, including newlines, on that side of the action. It keeps generated YAML tidy. Trimming too much joins lines and breaks YAML.
8. What does .helmignore do?
It lists files to leave out of the packaged chart, using patterns like .gitignore. Exclude CI files, local values and anything secret.
9. What is NOTES.txt for?
It is a template rendered after install or upgrade and printed to the user, usually with how to reach the app. It is not applied to the cluster.
10. What does a file starting with an underscore mean in templates/?
Helm does not render it as a manifest. By convention _helpers.tpl holds named templates (partials).
11. How do you see what a chart will render?
helm template myrel ./mychart -f values-dev.yaml prints the manifests locally. Add --show-only templates/deployment.yaml to view one file.
12. What does helm lint check?
Chart structure, Chart.yaml fields, template rendering errors, and schema validation if a schema exists. Use --strict to fail on warnings.
13. What goes in the crds/ folder?
Plain CRD manifests. Helm installs them before other resources on first install, does not template them, and never upgrades or deletes them.
14. How do you package and publish a chart?
helm package ./mychart creates mychart-1.4.2.tgz. helm push mychart-1.4.2.tgz oci://registry.example.com/charts publishes it to an OCI registry.
15. What is the convention for naming values keys?
The Helm best practices guide says to use camelCase starting with a lowercase letter, such as replicaCount, and to prefer flat structures unless nesting groups related settings.
2 to 5 years: writing templates
16. Template a Deployment's image, replicas and resources from values.
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "mychart.fullname" . }}
labels:
{{- include "mychart.labels" . | nindent 4 }}
spec:
replicas: {{ .Values.replicaCount }}
selector:
matchLabels:
{{- include "mychart.selectorLabels" . | nindent 6 }}
template:
metadata:
labels:
{{- include "mychart.selectorLabels" . | nindent 8 }}
spec:
containers:
- name: app
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
resources:
{{- toYaml .Values.resources | nindent 12 }}
17. Why use include instead of template?
include returns a string, so you can pipe it into nindent or quote. template writes output directly and cannot be piped, which makes indentation hard to control.
18. Write a fullname helper that respects the 63-character limit.
{{- define "mychart.fullname" -}}
{{- if .Values.fullnameOverride -}}
{{- .Values.fullnameOverride | trunc 63 | trimSuffix "-" -}}
{{- else -}}
{{- printf "%s-%s" .Release.Name .Chart.Name | trunc 63 | trimSuffix "-" -}}
{{- end -}}
{{- end -}}
Kubernetes names for many resources must be DNS labels of 63 characters or fewer.
19. Why must selector labels never change between versions?
A Deployment's spec.selector is immutable. Changing selector labels makes the upgrade fail. Keep selector labels minimal (name and instance) and put version labels only in the general label set.
20. Which labels should every resource carry?
The recommended Kubernetes labels: app.kubernetes.io/name, app.kubernetes.io/instance, app.kubernetes.io/version, app.kubernetes.io/managed-by, plus helm.sh/chart.
21. How do you make a value mandatory?
image: {{ required "image.repository is required" .Values.image.repository }}
Rendering fails with the message if the value is empty.
22. How do you render an optional block only when enabled?
{{- if .Values.ingress.enabled }}
apiVersion: networking.k8s.io/v1
kind: Ingress
...
{{- end }}
23. What is the trap with default and boolean values?
default treats false, 0 and empty strings as empty. {{ .Values.enabled | default true }} returns true even when a user sets false. Put the default in values.yaml instead, or test with hasKey.
24. How do you loop over a map of environment variables?
env:
{{- range $key, $val := .Values.env }}
- name: {{ $key }}
value: {{ $val | quote }}
{{- end }}
Inside range, the dot changes to the current item. Use $ to reach the root, for example $.Release.Name.
25. What does with do, and what is its scope gotcha?
with sets the dot to a value and skips the block if it is empty. Inside it, .Values no longer works; use $.Values.
26. Why quote string values?
YAML turns unquoted yes, on, 1.10 or 0123 into booleans or numbers. Piping into quote keeps them strings, which matters for env vars and annotations.
27. How do you restart pods when a ConfigMap changes?
annotations:
checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}
The pod template changes whenever the rendered ConfigMap changes, so the Deployment rolls.
28. How do you include a file from the chart?
{{ .Files.Get "files/app.conf" | nindent 4 }} for one file, or {{ (.Files.Glob "files/*").AsConfig | nindent 2 }} to turn several files into ConfigMap data. Files under templates/ cannot be read this way.
29. When is tpl useful?
When a value itself contains template syntax, such as a hostname built from the release name. {{ tpl .Values.hostTemplate . }} renders it. Use it sparingly, since it makes values harder to read.
30. What does lookup return during helm template?
An empty result, because there is no cluster connection. Templates that use lookup must handle the empty case. It works during install and upgrade, and with --dry-run=server.
31. Write a minimal values.schema.json.
{
"$schema": "https://json-schema.org/draft-07/schema#",
"type": "object",
"required": ["image"],
"properties": {
"replicaCount": { "type": "integer", "minimum": 1 },
"image": {
"type": "object",
"required": ["repository"],
"properties": {
"repository": { "type": "string" },
"tag": { "type": "string" }
}
}
}
}
Helm validates merged values against it on install, upgrade, lint and template.
32. How do you declare a dependency?
dependencies:
- name: postgresql
version: "16.x.x"
repository: oci://registry-1.docker.io/bitnamicharts
condition: postgresql.enabled
Run helm dependency update to download it into charts/ and write Chart.lock. The version range shown is an example; pin what you have tested.
33. How does a parent pass values to a subchart?
Under a key matching the subchart name (or alias): postgresql.auth.database: app. Values under global are visible to every subchart as .Values.global.
34. What are import-values and alias?
alias lets you include the same subchart twice under different names. import-values copies values exported by a subchart into the parent's values.
35. Write a helm test pod.
apiVersion: v1
kind: Pod
metadata:
name: {{ include "mychart.fullname" . }}-test
annotations:
"helm.sh/hook": test
spec:
restartPolicy: Never
containers:
- name: curl
image: curlimages/curl
args: ["-fsS", "http://{{ include "mychart.fullname" . }}:{{ .Values.service.port }}/health"]
Run it with helm test myrel after install.
36. How do you add a pre-upgrade migration job?
Annotate a Job with "helm.sh/hook": pre-upgrade,pre-install, set "helm.sh/hook-weight" for ordering and "helm.sh/hook-delete-policy": before-hook-creation,hook-succeeded to clean up. Hook resources are not managed as part of the release.
37. How do you support several Kubernetes API versions?
Check .Capabilities.APIVersions.Has "policy/v1/PodDisruptionBudget" or compare .Capabilities.KubeVersion, and set kubeVersion in Chart.yaml to refuse unsupported clusters.
38. How do you unit test templates?
The community helm-unittest plugin runs YAML test suites that assert on rendered output. Many teams also render with helm template and validate against Kubernetes schemas using a tool like kubeconform.
Senior: chart design
39. How do you design values.yaml for other teams?
Expose what changes between environments (image, replicas, resources, ingress hosts, feature flags) and keep sensible secure defaults. Document every key with a comment, and add a schema so mistakes fail early.
40. When would you build a library chart?
When many services share the same Deployment, Service and labels pattern. The library holds the named templates; each service chart stays small and passes values. Version the library carefully, since a change reaches every consumer.
41. How do you avoid breaking users when you rename a value?
Support both keys for a few releases, fail with a clear fail message once the old key is removed, bump the chart's major version, and note it in the changelog.
42. Should secrets live in chart values?
No. Reference existing Secrets by name, or use an operator such as External Secrets or the Vault integration to create them. Values files end up in Git and in the release record.
43. How do you make charts safe by default?
Set a pod and container securityContext (non-root, read-only root filesystem, drop all capabilities), resource requests, and a dedicated ServiceAccount with automount off unless needed.
44. How do you sign and verify charts?
Helm supports provenance files with helm package --sign and helm verify. With OCI registries, many teams sign the chart artifact with Sigstore cosign. Installing by digest pins the exact artifact.
Authoring scenarios
45. A rendered Deployment fails with "mapping values are not allowed here". How do you fix it?
The indentation is wrong. Render with helm template --debug, find the line, and check the nindent number. Using toYaml ... | nindent N instead of hand-built blocks prevents most of these.
46. --set image.tag=1.10 deploys tag 1.1. Why?
--set parsed 1.10 as a number. Use --set-string image.tag=1.10 and quote the value in the template.
47. A teammate's chart hardcodes the namespace in every template. What is wrong?
The chart cannot be installed into another namespace with -n. Use {{ .Release.Namespace }} or omit the field so Helm sets it.
48. A subchart ignores your values. What do you check?
The key must match the dependency name or alias exactly, and the condition must be true. Run helm template and inspect, or helm show values on the subchart to confirm the key names.
49. The chart works in dev but fails lint in CI. Why?
CI may use --strict or a schema that dev skips, or a newer Helm version. Pin the Helm version in CI and run the same commands locally.
50. Two services copy-paste the same 400-line chart. What would you propose?
Extract shared templates into a library chart or a common base chart, keep service-specific values in each repo, and add tests so changes to the shared part are caught before release.
Practice task
Create a chart from scratch without helm create: a Deployment, Service and ConfigMap, a helpers file with name and label templates, a schema with two required fields, and a test hook. Then run helm lint --strict and helm template until both are clean. Related reading: Helm chart examples and version drift in shared Helm charts. Helm is taught in our CKAD course, in Kharadi, Pune or live online.
FAQ
What are Helm chart interview questions about?
Writing and maintaining charts: Chart.yaml, values design, template functions, helpers, schemas, dependencies, hooks and tests.
What is the difference between include and template in Helm?
include returns a string you can pipe into functions such as nindent; template writes output directly and cannot be piped.
What is values.schema.json?
A JSON Schema file that Helm uses to validate the merged values on install, upgrade, lint and template.
Which Chart.yaml apiVersion should I use?
v2. Chart API v3 exists in Helm 4 only as an experimental feature behind HELM_EXPERIMENTAL_CHART_V3.
How do I test a Helm chart?
Use helm lint, helm template with a schema validator, helm test hooks after install, and optionally the helm-unittest plugin in CI.
Does Helm upgrade CRDs?
No. CRDs in the crds/ folder are installed only on first install and are never upgraded or deleted by Helm.
How is this page different from the 70+ Helm questions?
The 70+ guide covers Helm usage and concepts. This page focuses on writing charts, with code for each answer.
References
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Angry
0
Sad
0
Wow
0