Cracks in the Foundation: Operating Cloud Foundry...
summary
Ten concrete operational failures and fixes for running Cloud Foundry: over‑engineered automation that never ships versus iterative deploys; plan for failures and run blameless postmortems; shift upgrade culture so you can patch regularly; push apps to prod early; capacity math for 3 AZs — run at about 67% capacity; use APM and performance tests; logs explode if debug stays on so add a custom firehose nozzle or filtering; expect false positives from traditional scanners; require product teams and on‑call ownership.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 2:02Automation is the solution to our problems!
- 6:37How do you expect the unexpected?
- 9:24How do you expeol plan for the unexpected?
- 12:22How do you change the culture around upgrades?
- 17:25What if we build it and nobody comes?
- 23:45But why is the hardware gone?
- 30:55What happens when regulators get involved?
- 35:23Logs gone wild!
- 38:48Building a perfect product team
- 39:05Building a perfect good product team
related talks
24mCracks in the Foundation: Operating Cloud Foundry in the Real World
35mHow to Cloud Ops Like a Boss
31mPut Your Money Where Your CF Is
29mThe Challenges of Taking Open Source Cloud Foundry to Production
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
32mOps in the Time of Serverless Containerized Webscale
31mA Developer’s Perspective on Cloud Foundry Operations: One Month in the Trenches
38mWhat Does It Take to Run Cloud Foundry at Enterprise Scale?