Panel Discussion
summary
Panelists report concrete outcomes: companies run roughly 90% cloud native workloads or about 70% in some teams, one team migrates a medical supplies system serving 1,500 hospitals onto Kubernetes and says it would have been a nightmare on traditional servers. They build internal tooling for CI/CD, test-data generation and cost guards, lean on platform engineering and GitOps, and cope with complexity via abstraction and GPT‑style help. Main barriers are data‑residency rules and scarce engineers who understand the problems beneath the abstractions.
AI-written summary · about
chapters (10)
- 0:00Kubernetes skills importance
- 5:03Cloud native adoption rates
- 10:00Kubernetes complexity challenges
- 15:16Cloud native adoption challenges
- 22:20Cloud native communities
- 27:57Cloud native future trends
- 30:05Generative AI role in Sri Lanka
- 38:18Learning cloud native advice
- 44:00Sri Lanka's cloud native benefits
- 49:20Final takeaways
related talks
24mPanel Discussion
46mPanel Discussion: Cloud native technologies and Kubernetes adoption in Bangladesh
42mMastering Kubernetes: Challenges, Strategies, and Best Practices
33mPanel: Kubernetes, Cloud Native and the Public Cloud [B]
41mTales of the mythical Cloud-Native Platform
50mJourneys To Cloud Native Architecture: Sun, Sea & Emergencies
15mOpening Keynote talk
08mKeynote: Kubernetes and Cloud Native: The Past, Present, and Future