Chart best practices

Structure templates/ so each resource definition resides in its own file, named with dashed notation reflecting the resource kind, e.g. foo-pod.yaml; use .yaml for files producing YAML output and .tpl for those producing none. Defined templates are globally accessible to a chart and all of its subcharts, so defined template names should be namespaced, as in {{- define "nginx.fullname" }}; creating charts via helm create is highly recommended since template names are then automatically defined per this best practice. Indent with two spaces, never tabs, chomp whitespace where possible, and avoid adjacent blank lines. Use {{- /* */}} template comments for documentation; # YAML comments stay visible during helm install --debug but can introduce rendering errors on sections where functions like required need values. Scope: Helm. Reviewed October 4, 2026.