Which statement about values.yaml is true?

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

Answer: (D)

In Helm charts, values.yaml serves as the configuration input for templates. It provides default values for things like replica counts, image tags, resource requests, and feature flags. These values are injected into the chart’s templates through the .Values object, so the actual Kubernetes manifests can be rendered with these settings.

The key point is that these defaults can be overridden when you install or upgrade the chart. You can supply your own values file or use --set to override specific keys, allowing customization without changing the templates themselves. This makes values.yaml the mechanism for flexible configuration across different environments.

The other statements point to different parts of a chart: metadata and dependencies are defined in Chart.yaml, the resources to deploy come from the templates, and release history is tracked by Helm’s release storage rather than by values.yaml.