What problem does it solve? Writing Helm chart templates involves subtle Go template syntax, whitespace control, and Kubernetes naming constraints that are easy to get wrong, leading to broken renders, invalid YAML, and failed deployments. ## Core Features & Use Cases - Named Template Conventions: Enforces a standard set of _helpers.tpl definitions (name, fullname, labels, selectorLabels, serviceAccountName, image) with the 63-character Kubernetes label limit applied. - Go Template Patterns: Provides correct usage of include, toYaml, nindent, with, required, default, and safe handling of user-provided file content versus tpl interpolation. - Hooks and Testing: Covers helm.sh/hook annotations with weights and delete policies, plus linting and rendering workflows via helm lint, helm template, and dry-run upgrades. - Use Case: When adding a new Ingress template to a chart, apply the conditional resource pattern, namespace handling, and checksum annotation conventions, then validate with helm template before committing. ## Quick Start Ask the assistant to write a Helm template for a Deployment with configurable resources and a ConfigMap checksum annotation, following the chart's _helpers.tpl conventions.
