Emissary-Ingress: Intro And Deep Dive
summary
Emissary‑ingress is a Kubernetes API gateway built on Envoy that generates the large Envoy configs for you and focuses on developer‑centric self‑service mappings separate from infra listeners and auth so teams don’t collide. It upgrades Envoy to Envoy 1.23 and adds HTTP/3 to downstream clients, introduced getambassador.io/v3 alpha CRDs, and plans V3 beta/final with CRD cleanup and consistent cluster settings. The project integrates incrementally with Envoy Gateway, briefly dropped v1 CRDs then reintroduces them, and ships tracing, rate‑limit and resilience extensions.
AI-written summary · about
chapters (6)
- 0:00Start
- 3:28Emissary Core Features
- 4:01Emissary is Ambassador Edge Stack's Open Core
- 9:38Self-Service Configuration Best Practices
- 12:50Configuring the Control Plane (again)
- 18:39Emissary and Envoy Gateway
related talks
30mEmissary-ingress: Intro and Deep Dive
17mLessons Learned: Four Years with Emissary-ingress and Envoy
21mEmissary-ingress: Version 4 and the Road Ahead
36mUsing Ambassador to Build Cloud-Native Applications
32mK8s-based API Gateway
20mBuilding an Edge Control Plane with Kubernetes and Envoy
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
33mEnvoy Gateway Project Update
