The Practices That Made Me Go 'Wow': What Every CNCF Project Can Learn From Envoy
summary
Envoy documents and enforces concrete practices: 350k lines of C++, ~400 extensions, ~1k contributors, a one-day review SLA routed by strict CODEOWNERS, and a weekly on‑call in Opsgenie that triages CI and stalled PRs. Risky changes sit behind runtime guards with a 3–6 month deprecation cycle and bots that auto‑create cleanup issues and tag original authors two releases later. CI runs sanitizers (ASan/MSan/TSan), protobuf fuzzing via libprotobuf mutator, OSS‑Fuzz at ~50 targets 24/7, and most PRs get feedback in ~40 minutes.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 1:49Envoy governance
- 8:52Secure rollouts in Envoy
- 12:03Testing automation
- 18:08Supply chain accountability
- 21:41Takeaways
- 24:53Q&A
related talks
10mLightning Talk: Who is Envoy
29mUnderstanding, maintaining and securing Envoy's supply chain
26mMaking Envoy Sustainable
18mThe CNCF & You - Growing Community in the CloudNative Landscape
17mLessons Learned: Four Years with Emissary-ingress and Envoy
13mClosing Remarks
44mBuilding On-Ramps for Non-Code Contributors in Open Source
30mBringing Continuous Delivery to Open Source