Hyper-Automate your Cloud Native Journey
summary
Shows how to replace brittle day-two scripting with Kubernetes Operators/CRDs and OpenShift so stateful services (MySQL, Postgres, Cassandra, streaming) encode domain logic, lifecycle and RBAC across clusters. Uses kubectl, kubelet, Helm for day‑one deployment but promotes operators for upgrades, multi‑version CRDs and portability. Cites teams stuck with 70–80 YAML files per app as common pain; demonstrates operators reduce manual steps and enable near‑seamless multi‑cloud migration with minimal rewrites.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker background
- 3:10Why Cloud native matters
- 14:44Microservices architecture basics
- 23:32Kubernetes orchestration explained
- 31:38Stateful vs stateless apps in Kubernetes
- 36:14Limitations of Helm charts
- 38:01Custom resources and operators
- 44:01Operator features and RBAC
related talks
40mHarnessing the Power of Open Source for Cloud Native Developm...
45mKubernetes Operators: Operating Cloud Native services at scale
37mDeploying applications to Kubernetes: never send a human to do a machine's job
43mLessons learned writing 10+ Kubernetes Operators
53mAutomating Stateful Applications with Kubernetes Operators
17mAnti-patterns for Kubernetes Operators
25mThe Absolute Beginner's Guide To Cloud Native
24mAutomating Stateful Apps with Kubernetes Operators