Panel Discussion: Cloud Foundry Test Kitchen
summary
Panel reevaluates moving Cloud Foundry onto Kubernetes with concrete artifacts: working proofs using Quarks, project ireenie and a CF Operator that run containerized Cloud Foundry in production for a few customers today but not yet full feature parity with BOSH/Diego. Key gaps are operator ergonomics, ordered rollout semantics (ordered extended sets), multi‑cluster control planes at scale, and feature parity for enterprise workloads; a BOSH lifecycle SIG and migration recipes exist and several vendors are shipping or piloting distributions.
AI-written summary · about
chapters (12)
- 0:00Introduction and panel setup
- 1:52From blending to Test Kitchen
- 8:41Current state of Cloud Foundry and Kubernetes
- 16:09Developer vs operator perspectives
- 21:55Personas and operational models
- 27:13Enterprise readiness and production scale
- 31:56Developer experience beyond pushing code
- 36:37Unified programming models and innovation
- 41:54Feature parity and future capabilities
- 49:06Community engagement and outreach
- 57:32Cultural differences and collaboration
- 1:02:49Next steps and closing remarks
related talks
30mPanel: Cloud Foundry and Kubernetes - The Blending Continues
23mCloud Foundry and Kubernetes: A Peanut Butter & Jelly Application
19mPaaS on Kubernetes: Journey of Making Cloud Foundry Kubernetes Native
30mCF^3 - Using Kubernetes as the Cloud Foundry IaaS
38mLet's Run Cloud Foundry on Kubernetes
28mCloud Foundry 101 for Kubernetes Users
31mCloud Foundry Container Runtime: BOSH-Powered Kubernetes
01h 02mCloudFoundry or Kubernetes/Kubo: Choosing the Right Platform for the Job