Many Cooks, One Platform: Balancing Ownership and Contribution for the Perfect Broth
Talkat KubeCon + CloudNativeCon Europe 2025 · on Wednesday, 2025-04-02· at 14:30· Level 0 | ICC Capital Hall | Room J·
summary
Built an internal developer platform for the Dutch judiciary (Evo Respra) on OpenShift 4.16 → 4.17, running across four clusters (2 dev, 2 prod) plus a management cluster, and migrating from an old container platform to a modular Respark platform. Teams face duplicated image builds (up to four per app) after moving builds into Azure DevOps pipelines and artifacts into Artifactory for registry, causing ownership friction with developer-tooling teams. Wins: a reworked microservices forum with agendas and invited contributions; losses: an SRE user group that failed to engage. Community, clear scope, and enabling teams prove decisive.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:36Why build a platform
- 8:52Services versus platforms
- 13:28Developer portals vs platforms
- 14:32Developers as contributors
- 15:57Bricks versus builds
- 16:41Team topologies
- 18:27Community at heart
- 19:31Rebuilding microservices meeting
- 21:37Failed user group experiment
- 24:26Platform vision and scope
- 26:55Summary
related talks
43mPlatform Engineering 101: Building Developer Platforms
31mPanel Discussion: Platform and Developer Productivity - Trends and Challenges
44mPlatform Engineering 101: Building Internal Developer Platforms
27mLessons from a Year with Backstage: What Worked, What Didn’t...
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
29mYour platform is not an island: building a platform for your ecosystem
40mLessons Learned Building Developer Platforms
42mPlatform Engineering 101: Building Internal Developer Platforms