Cloud Foundry Diego Update
summary
Diego replaces the old DEA and proves itself by running quarter million containers in validation, using core components: rep on each cell, BBS API, auctioneer for placement and the new locket for coordination; container runtime shifts to garden-runC with Guardian and optional Windows support via Wincy. Operators get instance identity credentials — short‑lived, rotated certs for mutual TLS between app instances — and a CF Diego Operator Toolkit ("cfdot") to inspect BBS/locket state; v2 plans require TLS, make locket mandatory, and pursue zero‑downtime updates and smarter rebalancing.
AI-written summary · about
chapters (9)
- 0:00Introduction to Diego
- 1:24Diego in Cloud Foundry
- 4:17Typical Diego deployment
- 7:29Cell VM evolution
- 10:17Isolation segments
- 13:53Instance identity credentials
- 21:19CF dot operator tool
- 25:11Next steps for Diego
- 28:19Q&A session
related talks
37mCloud Foundry Diego Overview
35mResource Management Ecosystem and Cloud Foundry - A Review of the State of the Art
31mThe Road to Persistence on Cloud Foundry Diego
28mDiego vs Eirini: How to Choose the Best Fitting Container...
33mCloud Foundry’s New .NET Capabilities
33mDocker and Cloud Foundry: The 3 Use Cases
21mA Retrospective on a Decade of Contributing to Cloud Foundry
10mCost Optimization in Cloud Foundry Through Economies of Scale