We Come From a Land of Runtimes
summary
Compares concrete runtime choices: Diego apps on BOSH VMs, apps on Kubernetes via Eirini, full CF-as-containers (CF containerization / CFE), or CF core on BOSH with apps on K8s. Calls out tradeoffs: double-container nesting causes debugging and security friction, Eirini preserves CF push developer experience while running pods, CF containerization turns every VM into a container, Gardener manages multi-cluster control planes. Recommendation hinges on workloads, operator expertise, and scaling limits; containerized CF core is promising but not yet battle‑hardened.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:08Why Cloud Foundry Application Runtime?
- 2:40How to Deploy and Live with CFAR
- 6:41How to Deploy and Manage Kubernetos?
- 9:42How about Both?
- 12:01Are you From Kubernetes' World?
- 14:43Cloud Foundry on Kubornetes
- 15:42How about No Nested Containers?
- 18:52Recap
- 20:02What to Choose?
related talks
25mPaving the Road to Eirini
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes
32mImplementing the Schedulers: A Look at the Internals of Diego...
22m"Cube" your Enthusiasm: Bringing CF and Kubernetes Together with...
30mCF^3 - Using Kubernetes as the Cloud Foundry IaaS
37mLet's Try All the CRI Runtimes: Part 2: Answering the Why Question!
30mContainers and Next Gen Infrastructure Ecosystem
35mWhat Container Runtime Do I Need?