Stenobird

Episode

Kubernetes Ingress & Gateway API Updates, with Lior Lieberman

Podcast
Kubernetes Podcast from Google
Published
Mar 11, 2025
Duration seconds
2715
Processing state
processed
Canonical source
https://e780d51f-f115-44a6-8252-aed9216bb521.libsyn.com/kubernetes-ingress-gateway-api-updates-with-lior-lieberman
Audio
https://traffic.libsyn.com/secure/e780d51f-f115-44a6-8252-aed9216bb521/KPod248.mp3?dest-id=3486674
JSON
/v1/public/podcasts/kubernetes-podcast-from-google/episodes/kubernetes-ingress-gateway-api-updates-with-lior-lieberman
Markdown
/podcast/kubernetes-podcast-from-google/kubernetes-ingress-gateway-api-updates-with-lior-lieberman.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/kubernetes-podcast-from-google/episodes/kubernetes-ingress-gateway-api-updates-with-lior-lieberman/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/kubernetes-podcast-from-google/kubernetes-ingress-gateway-api-updates-with-lior-lieberman.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

The Gateway API is evolving to handle complex networking needs like service mesh capabilities, reducing the need for custom CRDs. This discussion explores the transition from traditional Ingress to the Gateway API and how tools like Ingress2gateway simplify migration.

Topics

  • Kubernetes
  • Gateway API
  • Ingress
  • Service Mesh
  • CNCF
  • Cloud Native Networking
  • eBPF
  • OpenTelemetry

Highlights

  • Main idea: The Gateway API is a core Kubernetes API designed to provide better separation of concerns between infrastructure and application developers
  • Practical takeaway: Use Ingress2gateway to automate the conversion of legacy Ingress resources and custom annotations into Gateway API resources
  • Failure mode: Relying on complex, custom-annotated Ingress implementations can lead to fragmented, unmanageable networking configurations
  • Main idea: Service meshes remain essential for advanced microservices needs like identity-based authorization and request mirroring, even as Gateway API matures
  • Practical takeaway: For new Kubernetes deployments in 2025, the Gateway API should be the primary choice for ingress and traffic management

Chapters

  1. 1:00 Kubernetes Security News: An overview of Kubescape's move to CNCF Incubation and its role in Kubernetes posture management.
  2. 11:35 The Gateway API Persona and Structure: Defining the different roles and resources that make the Gateway API more efficient than traditional Ingress.
  3. 14:50 Simplifying the Migration Path: How Ingress2gateway addresses the complexity of migrating custom annotations and CRDs to the new API.
  4. 21:30 Gateway API vs. Service Mesh: Analyzing the overlap and the continued necessity of service meshes for observability and security.
  5. 31:25 Permission Boundaries and Security: The benefits of segregating cluster-level infrastructure permissions from user-level application permissions.
  6. 38:30 The Future of Ingress Migration: Discussing the impact of major providers like Nginx adopting Gateway API to lower the barrier to entry.