From Cloud Naive to Cloud Native – Avoiding Mistakes Everyone Does
summary
Companies treat Kubernetes like a VM instead of a platform, so expect to build an internal developer platform as a living product with a dedicated team that runs hundreds of updates and integrates CI/CD, RBAC, network policies, readiness and startup probes, and operators. Migration choices matter—a quoted €30 million saving can cost years and retraining—and only about 27% of developers use Kubernetes daily. Start small, start by zero, avoid bespoke operators, and validate that the platform actually reduces toil.
AI-written summary · about
chapters (15)
- 0:00Thank you to our session recording sponsor!
- 1:56Moving to the Clouds
- 3:48The Cloud Native Pyramid
- 7:33Cloud Based vs Cloud Native
- 8:24Misconceptions Observations
- 13:53Mindset & Strategy
- 15:35You need to start by
- 19:40"Every" dev tool is critical
- 20:52The platforms you build will be used forever
- 23:06Teach pattern
- 24:03Development & Product Management
- 24:55Kubernetes
- 27:38Multi or Single Cluster
- 29:30Most important
- 30:41Summary
related talks
40mLessons Learned Building Developer Platforms
36mPractical Cloud Native: What Works, What Doesn't
41mTales of the mythical Cloud-Native Platform
45mKubernetes is Not for Developers...?
47mDo We Really Need Kubernetes? A Tactical Guide to Cloud Native
43m5 tips on creating modern, cloud native applications
53m(Mis)Understanding Cloud Native
42mCloud Native Applications