DevOps Bootcamp · Lesson

Helm 3 vs Helm 2: No More Tiller

What changed and why Helm 3 is client-only and safer.

Lesson 4 of 413 steps

Helm 3 vs Helm 2: No More Tiller is a free DevOps Bootcamp lesson on CoddyKit. This is lesson 4 of 4. Any 3 lessons of this learning path are free to read in full — after that, CoddyKit PRO unlocks every lesson, plus hands-on practice with a built-in code editor and a 24/7 AI tutor. It is part of the DevOps Bootcamp learning path, and your progress syncs across the web and the CoddyKit app. The DevOps Bootcamp course includes 4 lessons in total.

Helm Has a History

Today you use Helm 3, but Helm 2 came first and worked very differently. Knowing the shift helps you read older guides correctly. 📜

Helm 2 Had Two Parts

Helm 2 split into a client and a cluster-side component called Tiller. The CLI talked to Tiller, and Tiller talked to Kubernetes.

What Tiller Did

Tiller ran as a Pod inside the cluster. It received your commands and applied the actual resources on your behalf.

The Security Problem

Tiller often ran with broad cluster-admin rights. Anyone who reached it could effectively do anything, which was a real risk. 🔓

Helm 3 Removed Tiller

The headline change in Helm 3 is simple: Tiller is gone. The CLI now talks directly to the Kubernetes API, just like kubectl. 🎉

Client-Only Helm

Helm 3 is purely a client. It uses your kubeconfig and your own permissions, so there is no extra server component to secure.

Your Permissions Apply

Because Helm 3 uses your credentials, you can only do what your Kubernetes role allows. Access control becomes simple and standard.

Release Data Moved

Helm 3 stores each release's state as a Kubernetes Secret in the release's namespace, rather than in Tiller's old storage.

Namespace-Scoped Releases

In Helm 3, release names are unique per namespace, not cluster-wide. The same name can exist safely in two different namespaces.

Other Helm 3 Upgrades

Helm 3 also added optional values schema validation and native OCI registry support, on top of dropping Tiller entirely.

Why It Matters to You

If a tutorial mentions Tiller or helm init, it is for Helm 2. Modern Helm needs no init step, so you can safely skip that. 👍

Quick Check

What was the biggest architectural change in Helm 3?

Recap

Helm 3 removed Tiller, became client-only, uses your own permissions, and stores releases as namespaced Secrets. Safer and simpler. ✅

Free to start

Learn DevOps Bootcamp with an AI tutor — free

Write and run real code in your browser, get instant help from a 24/7 AI tutor, and pick up where you left off on the web or in the app.

Courses
142
Lessons
568

Frequently Asked Questions

Is the “Helm 3 vs Helm 2: No More Tiller” lesson free?

Yes — any 3 lessons of the DevOps Bootcamp learning path, including “Helm 3 vs Helm 2: No More Tiller”, are free to read in full here on the web. After that, CoddyKit PRO unlocks every lesson, plus interactive practice with a built-in code editor and a 24/7 AI tutor. The DevOps Bootcamp course includes 4 lessons in total.

What will I learn in “Helm 3 vs Helm 2: No More Tiller”?

What changed and why Helm 3 is client-only and safer. You practise DevOps Bootcamp 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 DevOps Bootcamp?

No prior experience is required. DevOps Bootcamp on CoddyKit is structured for beginners through advanced learners, so you can start here or from the beginning and move at your own pace. This is lesson 4 of 4.

How long does the “Helm 3 vs Helm 2: No More Tiller” 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 DevOps Bootcamp lesson?

Yes. Every DevOps Bootcamp 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

  1. The Pain of Raw kubectl apply
  2. Helm as apt/yum for Kubernetes
  3. Charts, Releases, and Repositories at a Glance
  4. Helm 3 vs Helm 2: No More Tiller
← Back to DevOps Bootcamp