The templates Directory and NOTES.txt
Where manifests live and how notes are rendered.
The templates Directory and NOTES.txt is a free Helm Academy lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Helm Academy learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.
Where Manifests Live
The templates directory is the heart of a chart. Every file here becomes a Kubernetes manifest after Helm renders it. 🧩
templates/
deployment.yaml
service.yamlThey Are Go Templates
Files in templates are not plain YAML: they are Go templates. Helm fills in the double-brace actions before sending them to the cluster.
spec:
replicas: {{ .Values.replicaCount }}One Resource Per File
By convention each file holds one resource type, named after it. This keeps a chart easy to read and navigate.
templates/serviceaccount.yaml
templates/ingress.yamlRendering Turns Them Real
At install time Helm renders every template, substituting values, then applies the resulting manifests to Kubernetes.
helm template ./mychartUnderscore Files Are Special
Files starting with an underscore, like _helpers.tpl, are never rendered into manifests. They hold reusable partials instead.
templates/_helpers.tplMeet NOTES.txt
A special NOTES.txt file in templates prints a friendly message after a successful install or upgrade.
templates/NOTES.txtNotes Are Templated Too
NOTES.txt is itself a template, so you can inject the release name or a real URL to show users how to reach the app.
Your release is named {{ .Release.Name }}.Notes Are Not Deployed
Unlike other files here, NOTES.txt creates no resource. Its only job is to print guidance to your terminal.
Reading Notes Later
You can resurface the rendered notes for an existing release any time with helm get notes.
helm get notes my-releaseSubfolders Are Allowed
You may group templates into subfolders; Helm walks the whole tree. The layout is up to you as long as files render to valid YAML.
templates/web/deployment.yaml
templates/web/service.yamlWhy This Layout Helps
A predictable templates folder plus NOTES.txt means anyone can open your chart and instantly know where the manifests are. 🎯
Quick Check
Let us pin down what NOTES.txt does.
Recap
The templates folder holds Go-templated manifests; underscore files are partials. NOTES.txt prints guidance and deploys nothing. ✅
Frequently asked questions
Is the “The templates Directory and NOTES.txt” lesson free?
Yes — the full text of “The templates Directory and NOTES.txt” is free to read here on the web, and the Helm Academy course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Helm Academy course, upgrade to CoddyKit PRO.
What will I learn in “The templates Directory and NOTES.txt”?
Where manifests live and how notes are rendered. You practise Helm Academy with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.
Do I need any experience to start Helm Academy?
No prior experience is required. Helm Academy on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.
How long does the “The templates Directory and NOTES.txt” lesson take?
Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.
Can I write and run code in this Helm Academy lesson?
Yes. Every Helm Academy lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.
All lessons in this course
- Generate a Skeleton with helm create
- Chart.yaml: Metadata and Versions
- The templates Directory and NOTES.txt
- Default values.yaml and the _helpers File