The Automation Challenge: Kubernetes Operators vs Helm Charts
summary
Three microservices (event, landmark, ticket-store) get deployed and evolved: Helm charts (helm create, starters, values.schema.json, umbrella/leader charts, Bitnami Postgres) bootstraps stateless services and quick prototypes with templated values, rollbacks and annotation-driven redeploys; an operator replaces the Postgres for event and a custom Operator SDK operator installs ticket-store from a GitHub-hosted chart, demonstrates backups/upgrades, RBAC integration and self-healing via operator when a deployment is deleted. The demo shows Helm for stateless apps and operators for stateful automation, and it works end-to-end.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:44Automation heroes
- 18:39Helm advantages
- 20:12Distinctive Helm Aspects
- 22:27Dealing with growing complexity
- 23:22Benefits of Using Operators
- 24:34What's next?
- 27:35Create an Operator?
related talks
32mThe Automation Challenge: Kubernetes Operators vs Helm Charts
30mThe Automation Challenge: Kubernetes Operators vs Helm Charts
29mHelm Your Way with Kubernetes
27mDeploying Databases on Kubernetes: Helm vs. Operators - Eric Schäffer and Manuel Swiercz
32mHelm your way with Kubernetes
40mCustom Microservices Deployments Using Helm Operators
35mOptimizing Kubernetes Deployments with Helm
27mAre you Helming it the right way? Helm challenges and its solutions