The Automation Challenge: Kubernetes Operators vs Helm Charts
summary
Demonstrates using Helm to package a Quarkus microservice plus Postgres, running commands like helm create and helm install + postgres and landmark deployed together, shows values files, checksums for auto-restarts and GitHub Pages as a chart repo. Moves Postgres management to an operator, installs Crunchy Data Postgres Operator, then generates an operator from the Helm chart with operator created from Helm chart with operator-sdk. Final demo runs a ticket-store app though one live demo has flaky behavior.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:47Some k8s features
- 3:53Microservices – k8s
- 4:20The story of a microservice
- 7:20Kubernetes package manager
- 8:28demo – Helm show time
- 15:32Helm advantages
- 17:34Distinctive Helm aspects
- 19:47Next steps
- 20:32What happens at system maturity?
- 21:13Benefits of using operators
- 23:23What's next?
- 24:35Create an operator?
- 25:14Final view
- 25:46From Helm charts to operators
- 27:05Create operator from Helm charts
- 28:22Takeaways
- 29:47Outro
related talks
32mThe Automation Challenge: Kubernetes Operators vs Helm Charts
47mThe 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
26mHelm your way with Kubernetes
35mOptimizing Kubernetes Deployments with Helm
28mOperators and Helm It Takes Two to Tango