Panel Discussion: Welcoming V3: Modernizing the Cloud Foundry API
summary
Cloud Foundry moves from a one-to-one v2 API to a modular v3 that exposes process and deployment resources so clients can orchestrate rolling deploys with zero downtime; the V3 Acceleration Team is converting resources (about 33% done) and the CLI refactor for v7 CLI is roughly 40% complete. New features include sidecars, metadata (27 resources, 6 new commands) and a push rewrite whose server‑side manifest support is the last hard piece; work reduces monolithic Ruby glue to clearer Rails‑style controllers and aims to improve performance and contributor onboarding.
AI-written summary · about
chapters (10)
- 0:00Introduction and panelists
- 2:57Why v3 was needed
- 5:44Onboarding experience in v3
- 7:36New v3 features explained
- 10:29CLI adaptation to v3
- 14:29v3 API documentation improvements
- 16:35v3 acceleration team collaboration
- 19:43External contributors to v3
- 22:15Roadmap and timeline for v3
- 25:06Q&A with the audience
related talks
21mA Retrospective on a Decade of Contributing to Cloud Foundry
50mVerizon's Cloud Native Transformation - Syam Suri, Verizon
27mGiving Cloud Foundry APIs Their Swagger Back
33mThe journey towards API Platform 3
01h 00mEvolving to Cloud Native
48mRefactoring of REST API
39mQ&A session
26mWhats new in AsyncAPI v3