Helm Chart Validator

Helm linting (helm lint) checks Chart.yaml structure and basic YAML syntax. Validation goes deeper: it checks template logic, parameterization best practices, brace balance in Go templates, and values.yaml structural correctness. This tool helps you catch issues before running helm template or helm install, without needing the Helm CLI installed.

Helm templates use Go's text/template syntax with double curly braces: {{ .Values.myValue }}, {{ include "chart.name" . }}, {{- if .Values.enabled -}}. The leading dash {{- removes preceding whitespace, and the trailing dash -}} removes following whitespace. Proper use of dashes prevents unexpected blank lines in rendered manifests.

nindent N prepends a newline and then indents each line by N spaces. It's used when including a multi-line helper (like a labels block) inside an existing indented block. For example: {{- include "mychart.labels" . | nindent 4 }} ensures the labels are properly indented within the metadata section, preventing invalid YAML indentation in the rendered output.

No. Image tags should always come from values.yaml via {{ .Values.image.tag }}. Hardcoding image tags in templates makes it impossible to override them at deploy time with helm install --set or -f custom-values.yaml. The best practice is to use {{ .Values.image.tag | default .Chart.AppVersion }} so the chart falls back to the app version if no tag is specified.

Resource requests tell the Kubernetes scheduler how much CPU/memory a Pod needs to be placed on a node. Resource limits cap the maximum usage. Without requests, the scheduler may place Pods on overloaded nodes. Without limits, a runaway container can consume all node resources and evict other Pods (OOM kill). Always set both requests and limits for production workloads.

No. All validation runs entirely in your browser using JavaScript. Your template YAML never leaves your machine. For full rendering validation, run 'helm template my-release ./chart' locally with the Helm CLI.