Episode
Platform Engineering, with Ben Good
- Published
- Aug 6, 2025
- Duration seconds
- 2055
- Processing state
processed- Canonical source
- https://e780d51f-f115-44a6-8252-aed9216bb521.libsyn.com/platform-engineering-with-ben-good
Actions
POST https://stenobird.com/v1/public/podcasts/kubernetes-podcast-from-google/episodes/platform-engineering-with-ben-good/transcription-requests
Idempotently request low-priority transcript generation for this episode.GET https://stenobird.com/podcast/kubernetes-podcast-from-google/platform-engineering-with-ben-good.md
Read the agent-friendly Markdown representation of this episode resource.
Summary
Kubernetes serves as a foundational 'platform for platforms,' providing the primitives necessary to build bespoke internal developer experiences. This discussion explores how to design platforms that prioritize developer usability and observability over forced compliance.
Topics
- Platform Engineering
- Kubernetes
- SRE
- Developer Experience
- Observability
- DORA Metrics
- Cloud Native
- Infrastructure as Code
Highlights
- Main idea: Kubernetes is a toolbox of constructs, not a finished platform, allowing engineers to build customized interfaces
- Practical takeaway: Use DORA metrics to measure both application development velocity and the effectiveness of your platform engineering
- Failure mode: Avoid 'naive abstractions' that hide infrastructure costs and usage patterns from the developers using the platform
- Practical takeaway: Successful platforms should provide 'free' capabilities like observability, logging, and security policies through seamless integration
- Failure mode: Forcing engineering teams onto a platform for the sake of governance often fails; design for user needs instead
Chapters
1:10Cloud Native News: Updates on AWS EKS scaling to 100k nodes and changes to the Bitnami catalog.3:45The Overlap of SRE and Platforms: Discussing how Kubernetes acts as a platform for building other platforms.6:00Kubernetes as a Toolbox: Why Kubernetes provides the necessary primitives but isn't a complete platform solution on its own.8:30Defining the Platform Interface: Exploring different ways to present platform capabilities, from YAML to custom document-based interfaces.13:50Observability and Visibility: The importance of plumbing metrics, logging, and failure rates directly into the developer experience.21:40Deployment Archetypes: Understanding the hierarchical layers of infrastructure from applications to global regions.29:05Designing for the User: Avoiding the trap of hiding costs and complexity, and focusing on serving the engineering organization's needs.