Learn Helm by installing real charts and building your own, one concept at a time.
Problem: TODO
Solution: TODO
TODO
TODO — 建議先完成 Kubernetes in Practice。
Part 1 — What is Helm?
- The Role of Helm in Kubernetes — Kubernetes has no idea which objects form one app; Helm packages them as charts and tracks installs as releases.
- Benefits and Limitations of Helm — seven benefits and five limitations: simpler deployments, consistent environments and rollbacks, weighed against templating complexity, chart security, in-cluster state and risky upgrades.
- Helm vs. Kustomize — templates and values vs. base and patches: the same change both ways, and when to use which.
- Helm Architecture — how developers, chart repositories and CI/CD fit together; the chart files and common commands; and what
helm installdoes, from rendering to the release Secret.
Part 2 — Installing Tools
- Installing Tools — a single-node kubeadm cluster plus Helm and k9s, via the companion Ansible tutorial.
Part 3 — Helm Fundamentals
- Exploring Artifact Hub — find charts, read a chart's page, and choose between charts for the same software.
- Managing Helm Repositories —
helm repo add,update,searchandpull, the local index cache, and OCI registries. - Installing the WordPress Chart — a default StorageClass, one
helm install, and what it created. Lab: open the site through a port-forward. - Exploring the Chart's Configuration —
helm showfor a chart's defaults,helm getfor what a release used. - Uninstalling a Release —
helm uninstall,--keep-history, and what uninstall leaves behind. - Cleaning Up Kubernetes Resources — the zombie volume problem, and a cleanup checklist. Lab: reinstall onto a leftover PVC and watch it fail.
- Setting Values via the CLI —
--setsyntax, the type trap, and which values survive an upgrade. - Setting Values via Files — values files with
-f, layering, precedence, and keeping them in Git.
Part 4 — Creating Our Own Helm Charts
- Creating Our Own Helm Charts — TODO