If You Know Heroku, You Can Use Kubernetes
summary
Claim: Heroku concepts map to Kubernetes operations — dyno → pod, slug → container image — and deploying needs concrete steps: write a Dockerfile, provision a node pool, run kubectl apply, and push images to a registry. Kubernetes provides rolling updates (defaults to 25% batches), Helm or operators for add‑ons, and observability into resources. Demo provisions a DigitalOcean cluster with nginx Ingress and cert‑manager via a custom rails‑app operator; TLS provisioning hits rate limits and the live deploy only partially succeeds.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 3:09Containers and Kubernetes
- 7:41Heroku dynos vs Kubernetes pods
- 12:40Heroku versus Kubernetes trade-offs
- 13:01Live demo setup
- 24:21Demo wrap-up and Q&A
related talks
25mFrom Heroku to Cloud Native in 7 Weeks
41mHow To Build Your Own Heroku in 2022?
55mHeroku PaaS Apps to Feature your Work in any Language
31mSimplifying Python Web App Operations: Automating K8s Ops with Open Source
01h 29mTutorial: Build Your Own Heroku With Cloud Native Stack
41mUnderstanding Kubernetes in a Visual Way
03h 41mKubernetes Basics - a live tutorial
32mOperating Rails in Kubernetes