GatewayAPI, 10 Years of Maturation for a New Kubernetes API
summary
Gateway API v1.0 is presented as Kubernetes-native CRDs that separate responsibilities: GatewayClass for infrastructure operators, Gateway for cluster operators, and route types like HTTPRoute/GRPCRoute for developers. It adds features such as cross-namespace opt‑in backend references, TLS termination without sharing org certificates, request mirroring and weighted traffic splitting, a conformity test suite for implementations (GCP, Contour, Envoy, etc.), and a migration helper that converts existing Ingress/CRD setups but requires manual review of generated manifests before production.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 10:38Ingress API problems
- 23:21Gateway API overview
- 31:27Resource deployment
- 41:19Implementation and adoption
- 45:10Q&A
related talks
50mGateway API, 10 Years of Maturation for a New Kubernetes API
50mGateway API, a Decade of Maturation for a New Kubernetes API
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
24mLeveraging Gateway API for Kubernetes Native API Management
43mGateway API: Beta to GA
36mGateway API The new way to travel north south