Next steps in the Cloud Foundry API and why...
summary
Cloud Controller splits the monolithic v2 app into top-level objects packages, droplets, processes and replaces v2 meta-magic with explicit controller actions and fetcher/query objects written in Ruby, making each endpoint testable and isolating transactions. API responses adopt a HAL-like shape, expose start stop scale endpoints that perform hidden work (scale applies instances/memory with rolling updates), and plan seamless v2→v3 mapping by creating v3 apps under the hood. v3 is marked experimental until CLI and clients consume it.
AI-written summary · about
chapters (9)
- 0:00Introduction to Cloud Foundry API
- 2:06Limitations in current API
- 3:51Codebase rigidity in v2
- 7:19V3 controller design changes
- 11:57API design improvements in v3
- 15:29Simplified query parameters
- 17:14Future features with v3
- 19:43Migration from v2 to v3
- 20:29Q&A session
related talks
22mDo More With Your Apps: Unleashing the Power of the V3 Cloud Controller API
26mHow Cloud Controller Makes the Foundry Go ‘Round
17mKeynote: State of the Project
01h 25mWhat's New in CloudFoundry
20mAdvancing the Future of Cloud Foundry
21mA Retrospective on a Decade of Contributing to Cloud Foundry
27mTOC-Ing Heads: Shaping Cloud Foundry’s Future
01mIntroduction: Cloud Foundry