The Automation Challenge: Kubernetes Operators vs Helm Charts
summary
Compares using Helm for packaging and templating versus operators for lifecycle and stateful maintenance, with a live ticket‑store: two Quarkus microservices plus a frontend, Postgres DB, and Helm charts published to GitHub Pages. Demonstrates helm create with starters, values.yaml for envs, chart dependencies for a shared Postgres, upgrades and rollbacks via helm revisions, then generates an operator with operator-sdk init --plugin=helm to hand DB maintenance to an operator; operator recreates a deleted deployment automatically, showing it works.
AI-written summary · about
chapters (5)
- 0:00Start
- 15:46Prototype
- 19:09Benefits of Using Operators
- 20:05Operators can be used to create backups or for configuring your cluster
- 23:52From Helm Charts to Operators
related talks
30mThe Automation Challenge: Kubernetes Operators vs Helm Charts
47mThe Automation Challenge: Kubernetes Operators vs Helm Charts
27mDeploying Databases on Kubernetes: Helm vs. Operators - Eric Schäffer and Manuel Swiercz
29mHelm Your Way with Kubernetes
28mOperators and Helm It Takes Two to Tango
32mHelm your way with Kubernetes
27mDay 2 Operations of Helm Charts
26mHelm your way with Kubernetes
