This is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
summary
Cloud Foundry struggles usually trace to process not code: teams lacking automation or training, 137 releases per month across projects overwhelms manual ops, and one case shows a platform run like “75% of one person.” Recommended fixes are concrete: build a concourse pipeline to deploy CF, treat the platform as a product with a product manager and ordered backlog, create sandbox environments and environment-promotion pipelines, pair/mob to raise bus factor, and keep an incident test suite so upgrades are tested before production.
AI-written summary · about
chapters (18)
- 0:00Introduction and context
- 2:09Cloud Foundry is difficult to operate
- 3:38Lack of dedicated platform team
- 5:27Cutting corners on training
- 7:14Treat platform as a software product
- 10:53Customize platform to needs
- 12:38Collaboration and knowledge sharing
- 14:05Platform perceived as unreliable
- 15:30Testing upgrades in production
- 16:35Big batch releases cause issues
- 18:05Problems further down the stack
- 19:09Sandbox environments for testing
- 20:56Environment promotion and continuous delivery
- 21:39Documenting incidents and solutions
- 22:43Helping other teams improve
- 24:10Technology alone doesn’t transform
- 26:44Q&A: Convincing cross-functional teams
- 29:20Q&A: Cloud Foundry testing best practices
related talks
30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
26mSkilling Up: How to Effectively Grow a Cloud Foundry Organization - Steve Greenberg, Resilient Scale
19mKeynote: Confessions of a Cloud Foundry PaaS Product Owner: How to Create a Successful Devops Team
54mCloud Native Culture
22mCrossing the CI/CD/DevOps Chasm - Miranda LeBlanc, Liberty Mutual
06mThe Gold Standard in Platform Engineering: Cloud Foundry :)
44mNine Ways To Fail at Cloud Native
06mLow Growth DevOps