Chart.yaml Metadata
What you'll learn: How the Chart.yaml file serves as your Helm chart's identity card, containing essential metadata that Helm uses to manage, version, and install packages.
What Is Chart.yaml?
Every Helm chart contains a Chart.yaml file at its root—think of it as a passport for your Kubernetes application. This YAML file tells Helm (and anyone looking at your chart) what your package is, who made it, and how it relates to other charts. Without it, Helm cannot recognize your chart as valid.
Core Metadata Fields
The Chart.yaml structure includes several key fields:
apiVersion: Defines the chart API version (usually v2 for Helm 3).
name: Your chart's unique identifier—no spaces, lowercase preferred.
version: The chart's package version (follows semantic versioning like 1.2.3). This changes when you update the chart's templates or configuration.
appVersion: The version of the application your chart deploys (e.g., nginx:1.21.0). This is informational—it tells users which software version they're installing, separate from the chart packaging version.
Dependencies and Extended Metadata
dependencies: Lists other charts this chart requires. For example, a web app chart might depend on a PostgreSQL chart. Each dependency specifies name, version, and repository.
Additional identification fields include:
description: Human-readable summarymaintainers: Contact info for chart authorskeywords: Tags for searchabilityhome: Project website URLsources: Code repository links
Why This Matters
The separation between version and appVersion is crucial: you might fix a typo in templates (bump chart version to 1.0.1) without changing the actual application version (nginx:1.21.0). Dependencies ensure Helm installs prerequisite charts automatically.
Key Takeaway: Chart.yaml is the manifest that identifies your chart with versioning, dependencies, and metadata—Helm's foundation for managing releases and understanding what's being deployed.