Using Ambassador to Build Cloud-Native Applications
summary
Ambassador is a Kubernetes-native API gateway built on Envoy that maps Kubernetes annotations or CRDs (use CRDs going forward) to Envoy config, supports TLS termination or passthrough and SNI, and offers traffic shadowing and canary splits for live testing. Run as edge or daemonset for east‑west, use separate Ambassador ID per responsibility to avoid config collisions, beware the default 3 second timeout that caused 503s during pod rollovers, and note auth and per-service retries are in the paid pro features.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:44Monoliths vs microservices
- 2:10Ambassador API Gateway
- 3:54Key features and integrations
- 7:02Edge routing with Ambassador
- 10:52TLS termination and SNI routing
- 11:59Internal API gateway use cases
- 13:22East-west traffic routing
- 15:28Traffic shadowing for testing
- 16:54Telepresence integration
- 17:57Configuration options
- 19:43Lessons learned from deployments
- 24:17Dedicated instances per responsibility
- 24:59Timeout configs and troubleshooting
- 26:47Service discovery and load balancing
- 28:13Getting started and best practices
- 29:57Config as code and security
- 30:59Q&A: Ambassador vs Istio
- 33:45CRDs vs annotations
- 35:13Canary deployments and traffic splitting
related talks
36mUsing Ambassador to Build Cloud-Native Applications
20mBuilding an Edge Control Plane with Kubernetes and Envoy
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
30mEmissary-ingress: Intro and Deep Dive
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
05mKeynote: Envoy, the Engine for a Cloud Native Security Kernel
28mEmissary-Ingress: Intro And Deep Dive
39mEnvoy Gateway: The API Gateway in the Cloud Native Era