Helm — The Kubernetes Package Manager
Charts, releases and templating, explained from the ground up. Learn how Helm packages, versions and ships Kubernetes applications — and remember it with spaced repetition.
- flashcards
- 81
- flashcards
- per day
- ~10 min
- per day
- level
- Beginner → Intermediate
- level
- modules
- 5
- modules
What is Helm?
Helm is the package manager for Kubernetes. Instead of hand-applying dozens of YAML manifests, you install a chart — a versioned, parameterized bundle of templates — and Helm renders it into concrete resources and tracks the result as a named release.
That model unlocks the things raw kubectl apply makes painful: templated values for each environment, one-command upgrades and rollbacks, and reusable dependencies pulled from repositories or OCI registries. Helm 3 is client-only — there is no Tiller — so the security and lifecycle story is dramatically simpler than Helm 2.
This track breaks Helm into bite-sized, practical questions — from Chart.yaml and the templating engine to release revisions and provenance — and uses spaced repetition so the mechanics move from "I followed a tutorial once" to long-term recall.
5 modules, seed to bloom
Each module is a set of flashcards — 81 in total. Answer, review, and watch your knowledge grow from seed to full bloom.
Helm Basics & Architecture
Charts, releases, repositories, and what the Helm client does
16 cardsChart Structure & Templating
Chart layout, values, Go templates, functions, and named templates
17 cardsReleases & Lifecycle
Install, upgrade, rollback, revisions, hooks, and release status
16 cardsDependencies & Repositories
Subcharts, dependencies, chart repos, and OCI registries
16 cardsPackaging & Distribution
Packaging, linting, rendering, provenance, signing, and scaffolding
16 cardsSample questions
A taste of the real flashcards. Pick an answer, then reveal the explanation.
What is Helm in the Kubernetes ecosystem?
- AA package manager for Kubernetes applications
- BA container runtime for scheduling Kubernetes pods
- CA service mesh for routing traffic between pods
- DA monitoring agent for collecting Kubernetes metrics
Which chart directory holds the manifests Helm renders?
- Atemplates/, whose files are rendered and applied
- Bmanifests/, which Helm does not treat specially at all
- Cresources/, which is not a directory Helm looks for
- Dcharts/, which holds dependency charts rather than templates
What does the helm upgrade command do to an existing release?
- AIt applies a new chart or values as a revision
- BIt deletes the release before installing it again
- CIt rolls the release back to its previous revision
- DIt only refreshes the cached chart on the client
A chart with two subcharts is installed. How many releases?
- AOne, because the parent and its subcharts share a release
- BOne per chart, so a subchart can be upgraded on its own
- COne per namespace that any of the resources land in
- DTwo, plus a parent release that tracks the other two
Learn it once, keep it for good
Answer a question
Each card is one practical concept with multiple options. Pick what you think is right.
Get the full answer
See the correct option plus a clear explanation, and a link to deeper docs when one is available.
Review at the right time
A spaced-repetition engine (SM-2 or FSRS) resurfaces each card just before you would forget it.
Why Helm is worth your time
The standard way to ship to Kubernetes
Most teams package and deploy with Helm. Reading and writing charts is a baseline cloud-native skill.
Upgrades and rollbacks without fear
Understanding releases and revisions means you ship changes — and undo them — with one command.
Templating that scales
Values, helpers and conditionals let one chart serve dev, staging and prod without copy-paste.
Interview-ready
Charts, releases and the Helm 2→3 differences are common DevOps and platform interview topics.
Common questions
Do I need to know Kubernetes first? +
A working grasp of Pods, Deployments and Services helps, since Helm packages exactly those. If you are new to Kubernetes, the Kubernetes track pairs well with this one.
Is this Helm 2 or Helm 3? +
Helm 3. The deck reflects the current client-only architecture (no Tiller), OCI registries and Chart.lock — Helm 2 specifics appear only where the contrast matters.
Is it free? +
Yes, completely free. No registration or credit card is required, and all your progress is stored locally in your browser.
How long does it take? +
About 10 minutes a day. Spaced repetition means short, frequent sessions beat cramming — most learners feel comfortable with charts and releases within a couple of weeks.
Ready to master Helm?
Plant your first seed today. Ten minutes a day is all it takes to package and ship Kubernetes apps with confidence.