Which statement describes the role of chart.yaml?

• A. It contains Kubernetes manifests.
• B. It defines the chart's metadata and dependencies.
• C. It lists all resources in the release.
• D. It stores release history.

Answer: (B)

chart.yaml defines the chart itself by describing its identity and how it connects to other charts. It contains metadata such as the chart’s name, version, and description, plus a dependencies section that lists any other charts this chart relies on. This is essential for Helm to identify the chart, manage its versions, and automatically pull in required subcharts during install or upgrade.

Kubernetes manifests aren’t stored in this file; they live under the templates directory and are rendered into manifests as part of the chart rendering process. The chart.yaml does not list every resource in a release; that list comes from the rendered templates and the release content. Release history is not kept in the chart file either—it’s maintained by Helm in the cluster’s storage (like ConfigMaps/Secrets) as you install or upgrade releases.