Securing Kubernetes Edge Traffic using TLS Encrypted Gateway
summary
Demonstrates using Gateway API v1.0 GA with cert-manager issued TLS certificates and a Let’s Encrypt ACME cluster-issuer to auto-create secrets and renew certs (cert-manager claims ~18 billion downloads/year). Shows a live Gateway with TLS listeners, HTTP and TLS-protected TCP routes, and a backend echo service; OpenSSL confirms TLSv1.3 and the demo’s connections terminate at the Gateway while backend traffic is optional plaintext or end-to-end TLS. Includes referenceGrant for cross-namespace secret access.
AI-written summary · about
chapters (17)
- 0:00Introduction and speakers
- 1:30Basics of TLS certificates
- 3:41Kubernetes and declarative approach
- 5:06Cert-manager for TLS management
- 7:52North South vs East West traffic
- 9:20Limitations of Ingress API
- 10:02Gateway API overview
- 12:37Gateway API personas
- 15:06TLS certificates with cert-manager
- 16:31Encrypted Gateway architecture
- 18:16Demo setup and prerequisites
- 20:49Live demo: HTTP route with TLS
- 27:13Live demo: TCP route with TLS
- 30:25Reference Grant for cross-namespace secrets
- 31:28Securing East West traffic with GAMMA
- 33:36Key takeaways and conclusion
- 34:42Q&A session
related talks
27mProviding secure Ingress into a multi-tenanted cluster using GatewayAPI
15mCertificates in Kubernetes
41mEffortless Secure and Control Traffic Using Kubernetes Gateway API for Ingress, Egress an...
47mGatewayAPI, 10 Years of Maturation for a New Kubernetes API
06mGet To Where You're Going With Kgateway
01h 00mGateway API: Basics, Nuance, and the Real World
15mSecuring your app's communications with Kubernetes, Azure Key Vault, and TLS certificates
10mLightning Talk: Make Way for the Gateway