Blueprints of Innovation: Engineering Paved Paths for a User-friendly Developer Platform
summary
An internal developer platform for a single-cloud strategy runs centralized, multi-tenant Kubernetes clusters per environment managed by a Delivery Engineering team, with tenant operators mapping tenants to namespaces and preventing namespace creation by teams. A templating engine creates GitHub repos, injects Dockerfiles, OpenTelemetry, Vault secrets, Drone CI and Argo CD + GitOps manifests, and aims for day-zero in under 10 minutes (one manual cloud-account gate). GA landed spring 2023 with wide adoption; updates land as PRs via templating and moved YAML into Helm charts to reduce drift.
AI-written summary · about
chapters (10)
- 0:00Introduction and platform overview
- 3:54What is an Internal Developer Platform
- 8:26Platform architecture and components
- 12:01Runtime and cloud account strategies
- 16:15Continuous delivery with GitOps
- 18:45The role of the developer portal
- 20:32Platform as a product approach
- 23:20From MVP to GA launch
- 26:30Crossing the adoption chasm
- 28:14Lessons learned and wrap-up
related talks
44mPlatform Engineering 101: Building Internal Developer Platforms
39mJourney to an internal developer platform @ d.velop
44mIs Platform Engineering a hype? Let's build a platform together!
28mWhat's Next in Platform Engineering
31mPlatform Engineering's Inferno
37mBuilding a Managed Platform While Maintaining a Good Developer Experience
44mPlatform Engineering in action
39mPlatform Engineering as a (Community) Service