What is a Helm chart?

WHAT THIS TESTS Whether you grasp the difference between raw Kubernetes YAML and a reusable, parameterized package, and why teams reach for Helm.

A GOOD ANSWER COVERS A Helm chart is a packaged set of templated Kubernetes manifests. It contains a templates directory of YAML with Go templating placeholders, a values.yaml holding default configuration, and a Chart.yaml with name, version, and metadata. When you install it, Helm renders the templates against the supplied values to produce concrete manifests and applies them to the cluster as a named release that has revision history. The core problem it solves is duplication and drift: without it you copy near-identical Deployment, Service, and ConfigMap YAML for every app and every environment, hand-editing image tags and replica counts. A chart lets you define the shape once and vary just the values, while also packaging, versioning, sharing via repositories, and atomically upgrading or rolling back.

COMMON WRONG ANSWERS Calling Helm a CI/CD system or a GitOps tool, equating a chart (the package) with a release (the installed instance), or thinking Helm replaces kubectl entirely rather than templating what it submits.

LIKELY FOLLOW-UPS What is the difference between a chart, a release, and a revision? How do you override values? What lives in Chart.yaml versus values.yaml?

ONE CONCRETE EXAMPLE Instead of maintaining three copies of a Deployment with replicas hardcoded to 1, 2, and 10 for dev, staging, and prod, you write one Deployment template with replicas set to a values key. You then install the same chart three times with different values files, and each becomes a tracked release you can upgrade or roll back independently.