Kubernetes in the 2nd Decade

Transcript

1. Kubernetes in the Second Decade KubeCon, Chicago November, 2023 Tim Hockin, Google @thockin (with help from many people!)
4. “...the next trillion core hours...” Jago Macleod @jagosan
5. AI / ML
6. “AI/ML will increase compute resource usage and the requirement to manage those workloads effectively and efficiently.” Janet Kuo @janetkuo
7. “Inference is the new web app.” Clayton Coleman @smarterclayton
8. “The impact of AI/ML will be on the same scale as the impact of the internet itself.” Tim Hockin @thockin
9. “I hope AI / ML can help us to optimize the testing, debugging, and supportability [of Kubernetes].” Dawn Chen @dchen1107
10. Clusters
11. “Multi-cluster is unavoidable, and for many, it's already the reality.” Jeremy Olmsted-Thompson @JeremyOT
12. “Clusters are limiting, users need to work at a higher level.” Jeremy Olmsted-Thompson @JeremyOT
13. “...maybe not clusterless, but less cluster.” Tim Hockin @thockin
14. “We're over-indexing [on multi-cluster], instead of making individual clusters reliably run all kinds of workloads at once.” Wojciech Tyczynski @wojtek-t
15. Complexity & Reliability
16. “...trying to do everything...” Antonio Ojea @aojea
17. “...trying to solve all issues for everyone...” Dawn Chen @dchen1107
18. “All of us [maintainers] underestimate the cost [of complexity] for users, and I perceive it as the biggest existential threat.” Wojciech Tyczynski @wojtek-t
19. “I don't think the Rails equivalent for K8s has emerged yet ... to solve this complexity by removing unnecessary choices.” Michael Taufen @mtaufen
20. “The big risk is its current complexity.” Tim Bannister @sftim
21. “We should focus on keeping the core small and stable.” Maciej Szulik @soltysh
22. “Avoid gridlock or calcification.” Jordan Liggitt @liggitt
23. “Kubernetes won not because it’s the best at any specific workload, but because it can run almost everything reasonably well.” Clayton Coleman @smarterclayton
24. “Kubernetes won not because it’s the best at any specific workload, but because it can run almost everything reasonably well.” Clayton Coleman @smarterclayton
25. “We’ve got to say no to things today, so we can afford to do interesting things tomorrow.” Tim Hockin @thockin
26. “Next generation operators are less likely to be experts in Kubernetes ... reliability and security are more important than new features.” Jago Macleod @jagosan
27. “Workloads on Kubernetes have evolved from casual to critical, including life safety, healthcare, telco, and public sector.” Jago Macleod @jagosan
28. “Keeping (or increasing) the [quality] bar in core is more important than any other feature that we may add.” Wojciech Tyczynski @wojtek-t
30. Ecosystem
31. “Paradox of Choice - too many choices actually limits our freedom, [we need to] help users choose or avoid the need to choose.” Janet Kuo @janetkuo
32. “We probably gotta shrink the landscape to stay sustainable.” Davanum Srinivas @dims
33. “It's hard to find what to plug in to Kubernetes and the problem gets worse the bigger the ecosystem grows.” Tim Bannister @sftim
34. “The growing CNCF landscape indicates a lack of standards. This creates compatibility and operational complexities.” Dawn Chen @dchen1107
35. “The ecosystem has flourished, but I see fewer learnings and patterns being brought back to Kubernetes.” Michelle Au @msau42
36. “...the big tent of openstack is a good example of how this can go wrong.” Antonio Ojea @aojea
37. “Kubernetes should stay unfinished.” Tim Bannister @sftim
39. “Come to the booth and tell me why I am wrong!”