Goodbye Ingress - Hello Gateway API
summary
Gateway API replaces Ingress with concrete resources: Gateway class deployed by Cilium, a Gateway (LoadBalancer IP assigned) and HTTP/TLS/GRPC/TCP/UDP routes. Demo shows cert-manager issuing a wildcard TLS via cert-manager, an HTTP route that returns a 301 to HTTPS and a working 50/50 traffic split between two service backends. Observability uses Hubble to trace requests. Cilium’s native routing and eBPF yields about a 25% throughput gain. Notes mention Envoy ARM build issues and occasional 503s when colocated.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:26Application routing basics
- 5:40Existing Ingress API overview
- 7:06Gateway API introduction
- 9:16Gateway API personas and roles
- 13:53Migrating Ingress rules
- 15:00Cilium CNI features
- 18:34Gateway API Envoy issues
- 20:21Demo prerequisites
- 21:47Deploying Gateway API
- 24:58Routing traffic to services
- 27:34HTTPS and TLS setup
- 29:22Traffic splitting demo
- 31:06Observing traffic with Hubble
- 33:13Q&A session
related talks
33mExiting Ingress With the Gateway API
28mBeyond Kubernetes Ingress (with Gateway API)
01h 00mGateway API: Basics, Nuance, and the Real World
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
06mGet To Where You're Going With Kgateway
36mGateway API The new way to travel north south
26mSIG Network Intro and Updates
28mApplication delivery on k8s - the past, present and future
