Leveraging Gateway API for Kubernetes Native API Management
summary
Claims a Kubernetes-native API management platform built on Gateway API with multiple releases over two years, using GatewayClass and HTTPRoute to separate infra, cluster operators and app teams. Replaces flat Ingress configs to add declarative CRDs, a control plane, GitOps, portal, observability and policy hooks. Notes concrete gaps in Ingress (fine‑grained mTLS, non‑HTTP protocols) and shows rolling strategies like 95/5 traffic split and an example service on port 880.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:16Agenda
- 3:45Ingress Configuration
- 4:31Ingress Security
- 5:21Limitations
- 5:55Routing Limitations
- 7:07Vendor Annotation
- 8:51Resource Model
- 10:35Sample Configuration
- 10:49Instantiate Gateway
- 11:09Application Developers
- 12:00Examples
- 13:04Recap
- 13:22Gateway API vs API Management
- 14:55API Management Requirements
- 19:19Reference Architecture
related talks
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
26mStreamlining API Governance: Kubernetes Native API Management
28mApplication delivery on k8s - the past, present and future
25mgRPC API Management With a Kubernetes Native API Management Platform
10mLightning Talk: Make Way for the Gateway
32mTaking Back Control of Your APIs with Gateway API
36mGateway API The new way to travel north south
27mEnterprise API management in agile integration