Kubernetes Podcast from Google GKE 10 years and SIG Networking, With Antonio Ojea
17 snips
Oct 1, 2025 Antonio Ojea, a software engineer at Google and core maintainer of Kubernetes, dives into the fascinating world of networking in this discussion. He shares insights on transitioning from traditional networking to software-defined virtual networks. Antonio explains Dynamic Resource Allocation for virtual IPs and the complexities of integrating Kubernetes with existing systems. He also addresses the progress and adoption challenges of the Gateway API, and how AI workloads are reshaping networking requirements. Expect a deep dive into the future of Kubernetes networking!
AI Snips
Chapters
Transcript
Episode notes
Treat Cluster As Its Own Routing Domain
- Treat each Kubernetes cluster as an autonomous routing domain and define clear ingress and egress points.
- Use controllers or Gateway API for complex ingress and CNI CRDs for egress/firewall needs.
Egress IPs Are A Distributed Systems Problem
- Egress IP stability is a hard distributed problem and lacks a single Kubernetes standard today.
- Dynamic Resource Allocation (DRA) could model virtual IPs and NAT pools as requestable resources to solve this.
Model Network Primitives As Kubernetes Resources
- Model special networking needs (like NAT pools or virtual IPs) as Kubernetes resources so pods can request them.
- Use DRA primitives to implement pools and let controllers assign IPs dynamically to deployments.