K8s-based API Gateway
summary
Ambassador is a Kubernetes-native API gateway that controls an Envoy proxy data plane, exposes many services behind a single load balancer (avoiding one ELB per service), and keeps state in Kubernetes rather than an external DB. Configuration moves from configMaps/annotations in older versions to CRDs in 0.70+, supports traffic shadowing and canary routes, TLS via k8s Secrets, external authentication or paid Ambassador Pro, and multi-cluster routing via Ambassador ID.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:08Background
- 2:08Kubernetes
- 7:43Ambassador
- 8:29How does it work
- 9:23What does it provide
- 10:14How is it different
- 11:51Configuration
- 13:42Configuration of Ambassador
- 19:27Edge Routing
- 22:54Kubernetes Routing
- 25:27General Tips
- 28:44References
- 30:03Questions
related talks
30mEmissary-ingress: Intro and Deep Dive
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
17mSeamless AI-as-a-Service across Kubernetes Clusters With Envoy AI Gate...
28mEmissary-Ingress: Intro And Deep Dive
03h 18mHands-On with an Envoy API Gateway, Now with GraphQL!
06mGet To Where You're Going With Kgateway
33mEnvoy Gateway Project Update