Providing secure Ingress into a multi-tenanted cluster using GatewayAPI
summary
Shows a Kubernetes-native pattern that wires cert-manager, external-dns, and Kong Ingress controller with GatewayAPI so HTTP(S) and gRPC(S) routes are created from plain manifests; gateway resources (cluster operator) control listeners and allowed namespaces while HTTPRoute/GRPCRoute (tenants) request routing. Demo creates gateways, issues Let's Encrypt certs, and adds Route 53 records automatically; good routes are accepted and routed, bad routes are rejected by listener/label checks enforced via RBAC and Hierarchical Namespace Controller.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:29Multi-tenancy basics
- 3:32Gateway API overview
- 9:09Gateway API for multi-tenancy
- 14:25Live demo
- 23:56Summary
- 25:01Q&A
related talks
28mBeyond Kubernetes Ingress (with Gateway API)
35mGateway API: The Illustrated Guide to the Future of Kubernetes Networking
28mApplication delivery on k8s - the past, present and future
01h 00mGateway API: Basics, Nuance, and the Real World
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
29mGateway API: The new Kubernetes Ingress that Unifies Load Balancing and Network Configs
43mKubernetes Ingress and API Gateways
32mGateway API: A New Set of Kubernetes APIs for Advanced Traffic Routing