Lessons Learned: Four Years with Emissary-ingress and Envoy
summary
Emissary-ingress is an opinionated Kubernetes-native gateway built on custom-built Envoy that after four years runs in thousands of installations; the team kept up with 62 releases, three major API versions and chose to standardize on CRDs only (dropping file and ConfigMap options). Early custom auth became Envoy’s http ext_authz but shipping a fork costs time and makes security updates hard; building and testing Envoy benefits from beefy hardware, and wasm/Lua look worth evaluating before forking C++.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 4:22Being opinionated
- 5:22Learning curve
- 8:47Creating a curriculum
- 10:43Managing security releases
- 13:45Community support
- 14:55Recap
- 15:35Recommendations
related talks
30mEmissary-ingress: Intro and Deep Dive
28mEmissary-Ingress: Intro And Deep Dive
33mGet to know Envoy - the modern proxy for cloud-native infrastructure - Baptiste Collard
26mMaking Envoy Sustainable
22mUnlock Kubernetes & Envoy: Master Your API Ecosystem!
33mThe End of a De...
06mOpening Remarks
21mDeep Dive: Envoy