Panel: Cloud Foundry and Kubernetes - The Blending Continues
summary
Panelists map concrete paths for combining Cloud Foundry and Kubernetes: experiments like Irene/Irene II test replacing Diego with Kubernetes scheduling, teams consider replace Diego with Kubernetes and whether to offload potentially 80% of undifferentiated plumbing to k8s and Knative, then reallocate effort to higher-level developer APIs. Proposals include using Kubernetes-native components via public APIs, a single Cloud Foundry control plane over many clusters, function-as-a-service integration with function-as-a-service with scale-to-zero, and certification by API conformance and exhaustive tests.
AI-written summary · about
chapters (9)
- 0:00Introduction to blending discussion
- 1:02Lessons learned from blending
- 5:36Bringing Cloud Foundry to Kubernetes
- 9:24Adopting Kubernetes components
- 13:38Future of Diego and Irene II
- 16:51Exploring new use cases
- 21:29Customer benefits of blending
- 24:28How far will blending go
- 29:02Q&A and closing remarks
related talks
01h 06mPanel Discussion: Cloud Foundry Test Kitchen
40mPanel: Bringing The Cloud To Kubernetes - Moderated by: Nic Cope, Upbound
33mPanel: Kubernetes, Cloud Native and the Public Cloud [B]
07mTrigger’s Broom, or How I Learned to Stop Worrying and Love OS
27mTOC-Ing Heads: Shaping Cloud Foundry’s Future
22m"Cube" your Enthusiasm: Bringing CF and Kubernetes Together with...
30mCF^3 - Using Kubernetes as the Cloud Foundry IaaS
38mLet's Run Cloud Foundry on Kubernetes