CF^3 - Using Kubernetes as the Cloud Foundry IaaS
summary
A proof-of-concept implements a Kubernetes CPI for BOSH and runs Cloud Foundry releases as containers on a Kubernetes cluster; initial deploys succeed and apps can be pushed, but operational problems appear: BOSH expects stable VM IPs and post-install state while Kubernetes treats pods as stateless and ephemeral, and nested containerization plus storage-driver changes (aufs→overlay) break Diego/Garden. The project pauses for further work, the CPI is public, and fixes would require changes at the BOSH–k8s boundary.
AI-written summary · about
chapters (8)
- 0:00Introduction and experiment setup
- 5:56Why not use Kubernetes directly
- 8:05Bridging two different worlds
- 13:24Workflow state challenges
- 15:59IP address stability issues
- 18:12Nested containerization problems
- 22:51Pausing the experiment
- 25:40Future possibilities and Q&A
related talks
26mA Smooth Path to Cloud Foundry on Containers
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes
38mLet's Run Cloud Foundry on Kubernetes
06mHow CFCR tackles Day 1& 2 Ops for Production Kubernetes
19mPaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native
28mCloud Foundry 101 for Kubernetes Users
30mDeploying Kubernetes with Cloud Foundry and BOSH
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job