helm-validator

Validating a Helm chart before deploying involves linting Chart.yaml and templates, rendering manifests to check YAML syntax, and auditing securityContext and resources. This process produces a severity-based report with proposed remediations to catch errors early.

Checking Helm templates for missing securityContext and probes requires rendering the chart and analyzing the output Kubernetes manifests. The validation enforces required securityContext, resources, and probe rules for Pod and Deployment templates, flagging gaps in a structured report.

You can run an optional dry-run admission check on a Helm chart when cluster access is available. This validates the rendered manifests against the target Kubernetes cluster's admission controllers to surface deployment failures before application.

Linting Helm CRDs and validating schemas is best done by detecting Custom Resource Definitions within rendered manifests and checking their documentation and schema gaps. This ensures your custom resources conform to expected structural definitions before deployment.

Helm chart validation does not automatically apply fixes. It operates in read-only mode by default, generating a structured remediation-oriented report with explicit pass, warn, fail, and skipped statuses so you can manually apply the suggested corrections.

Helm charts fail to render with YAML syntax errors when template variables produce invalid manifest structures. Rendering templates to generated manifests and running YAML linting detects these syntax issues, allowing you to correct the Chart.yaml or values configuration.