Emissary-ingress: Intro and Deep Dive
summary
An Envoy‑based Kubernetes API gateway that focuses on developer‑centric self‑service routing and centralized auth, rate‑limit and observability, with production integrations for Istio/Linkerd and Consul. Project donated to CNCF in 2021, Emissary 2.0 ships a conversion layer (apixed) between getambassador.io v2 and v3 alpha1, and the team reports 30 releases, 2,300 commits and 7,500 users on Slack. Roadmap: input‑language cleanups (camelCase, durations, consolidated host and cluster config), eventual v3 CRDs and Emissary 3.0 that drops Envoy v2 transport; ongoing collaboration with the new Envoy Gateway.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:20Emissary 2021
- 2:50What is Emissary
- 4:23API Gateways
- 6:15SelfService Configuration
- 11:13Upcoming Changes
- 16:38Envoy Gateway
- 19:30Recap
- 23:13Questions
related talks
28mEmissary-Ingress: Intro And Deep Dive
17mLessons Learned: Four Years with Emissary-ingress and Envoy
21mEmissary-ingress: Version 4 and the Road Ahead
06mOpening Remarks
32mK8s-based API Gateway
36mUsing Ambassador to Build Cloud-Native Applications
33mEnvoy Gateway Project Update
20mBuilding an Edge Control Plane with Kubernetes and Envoy
