Taking Back Control of Your APIs with Gateway API
summary
CubeRnetes Gateway API provides a way to regain control of exposed services by separating responsibilities and applying governance where Ingress fell short. The talk shows installing the Gateway CRDs on minikube, creating a GatewayClass and Gateway, then an HTTPRoute to an echo service, adding plugins for rate limiting and API-key authentication, and using Ingress-to-Gateway migration tooling; it also notes there are 50+ implementations and demonstrates enforcing routes and global policies at the cluster edge to block shadow APIs.
AI-written summary · about
chapters (11)
- 0:00Gateway API intro
- 3:51External access evolution
- 7:41What is Gateway API?
- 9:07Key concepts and modularity
- 12:18Taking back API control
- 15:47Risks of exposed APIs
- 19:02Demo setup
- 21:57Deploying Gateway API
- 24:47HTTP route services
- 26:30Security policies
- 30:32Summary
related talks
28mBeyond Kubernetes Ingress (with Gateway API)
01h 00mGateway API: Basics, Nuance, and the Real World
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
24mLeveraging Gateway API for Kubernetes Native API Management
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
26mGetting Hands-On with the New Kubernetes Gateway API
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs