It (Only) Starts with Containers
summary
Containers are only the beginning: plain YAML duplicates work, Kustomize is feature-complete and fragile (no transactions, brittle patches), and Helm solves templating but leaks global template names and value interpolation problems. GitOps with ArgoCD/Flux automates apply, Pulumi replaces templates with real Java/TS/Python code and enables reusable infrastructure (but needs state locking), and Crossplane or custom controllers turn app specs into Kubernetes + cloud resources. A Pulumi-backed multi‑tenant PaaS with Traffic ingress, Fluent Bit, Prometheus, scale‑to‑zero (Doorman), and prewarmed JVM images proves the approach works in production.
AI-written summary · about
chapters (9)
- 0:00Introduction to application
- 1:46Limitations of raw YAML
- 6:55Kustomize for configuration
- 11:22Templating with Helm
- 17:24GitOps and automation
- 20:06Infrastructure as code
- 25:08Custom controllers
- 32:30The road to PaaS
- 41:38Conclusion
related talks
36mHow to make Kubernetes rhyme with prod readiness - Tiffany Jernigan and Matthias Haeussler
23mGitOps: yea or nay?
27mLightning Talk: GitOps, A Slightly Realistic Situation on Kubernetes with Flux
40mHarnessing the Power of Open Source for Cloud Native Developm...
45mKubernetes Operability Tooling
33mBlueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
35mPlays Well with Others: Composability for Cloud Native Applications
17mOwn your YAML: extending Kustomize via Plugins