Which statement best describes the purpose of values.yaml in a Helm chart?

• A. It defines the chart's metadata and dependencies.
• B. It lists all resources to deploy in the cluster.
• C. It holds configuration values for the chart that can be overridden.
• D. It stores release history.

Answer: (C)

Configuration values that drive the chart templates are provided by values.yaml. In a Helm chart, templates reference variables under .Values, so the defaults you put in values.yaml are used to render the final Kubernetes manifests. This setup makes the chart reusable across environments because you can customize behavior without editing the templates themselves. For example, you might define replicaCount and image.tag in values.yaml; when you install or upgrade, you can override them with --values myvalues.yaml or --set replicaCount=5 to produce a different deployment. The other aspects of a chart live elsewhere: chart metadata and dependencies are in Chart.yaml, the actual resources are created by the templates, and release history is managed by Helm, not stored in values.yaml.