Helm Your Way with Kubernetes
summary
Deploys a three-service ticketing system (frontend + two backends) using Helm3 charts, Bitnami PostgreSQL community charts and Helm3 templates plus values.schema.json validation; demonstrates both single-chart installs and an umbrella/leader-chart dependency approach, shows secrets referenced from chart values, and proves apps come up in the cluster. Then converts the DB lifecycle to an operator using the Operator SDK helm plugin, replacing Helm-managed Postgres with an operator-backed instance; notes scaling and stateful upgrades are harder with plain Helm and that operators add RBAC, CRDs and automated backups/restores.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:40The story of a microservice
- 2:25Automation heroes
- 3:55Helm demo
- 12:47Helm advantages
- 14:07Distinctive Helm aspects
- 15:57Dealing with growing complexity
- 16:59Benefits of using operators
- 17:42What's next?
- 18:42Demo
- 20:59Create an operator
- 21:40From Helm charts to operators
- 22:47Demo
- 26:15Takeaways
- 27:46Additional resources
- 28:49Outro
related talks
47mThe Automation Challenge: Kubernetes Operators vs Helm Charts
32mHelm your way with Kubernetes
26mHelm your way with Kubernetes
30mThe Automation Challenge: Kubernetes Operators vs Helm Charts
27mDeploying Databases on Kubernetes: Helm vs. Operators - Eric Schäffer and Manuel Swiercz
32mThe Automation Challenge: Kubernetes Operators vs Helm Charts
41mHelm - the Better Way to Deploy on Kubernetes
27mAre you Helming it the right way? Helm challenges and its solutions