Chart Structure and Directory Layout
You'll learn the standard file and folder organization that makes up a Helm chart, so you can navigate and build charts confidently.
What is a Helm Chart Structure?
A Helm chart is just a directory with a specific layout that Helm expects. Think of it like a recipe book: certain sections go in predictable places—ingredients up front, instructions in the middle, notes at the end. Similarly, Helm charts follow a convention that makes them portable and understandable.
Standard Chart Directory Layout
When you create or download a chart, you'll see this structure:
mychart/
Chart.yaml # Metadata about the chart
values.yaml # Default configuration values
charts/ # Directory for dependent charts
templates/ # Kubernetes manifest templates
deployment.yaml
service.yaml
_helpers.tpl # Template helpers (optional)
.helmignore # Files to exclude from packaging
Required Files
Chart.yaml: Contains the chart name, version, description, and other metadata. Without this, Helm won't recognize the directory as a chart.values.yaml: Default values that users can override during installation or upgrade.
The templates/ Directory
This is where your Kubernetes manifests live as templates. Helm processes these files, substituting values from values.yaml or user-provided overrides. Files starting with underscore (like _helpers.tpl) are not rendered as separate Kubernetes objects—they contain reusable template snippets.
The charts/ Directory
Holds sub-charts (dependencies). When your chart depends on another chart (like a database), Helm stores it here.
Key Takeaway: A Helm chart follows a predictable directory structure with Chart.yaml and values.yaml at the root, templates in templates/, and dependencies in charts/—organizing everything Helm needs to deploy and customize your application.