Understanding, maintaining and securing Envoy's supply chain
summary
Envoy depends on roughly ~60 external dependencies and about 170,000 lines of C++ in the trusted compute base, with data plane libraries like quiche and BoringSSL and a high-CVE outlier libcurl (about 14 CVEs since 2018). Maintenance relies on Bazel-based builds, an RSS-driven release watch, and integrity checks using SHA256 hashes and hashen for Python. Strategies include removing the kitchen-sink image by compiling out extensions, producing a BOM dashboard, and enforcing dependency policy with versioning, peer review and fuzz testing.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:30Envoy.debug_line binary analysis (Lines)
- 5:08Envoy debug_line binary analysis (Core vs. extensions)
- 5:39Envoy.debug_line binary analysis Organization
- 6:22Envoy.debug line binary analysis (CVE count 2018-now)
- 7:43Envoy debug line binary analysis (repository locations.bzl updates 2018-now)
- 8:15Envoy debug_line binary analysis (Tagged releases 2018-now)
related talks
36mEnhancing Envoy: Certificate Handling at the Edge
36mEnhancing Envoy: Certificate Handling at the Edge
31mThe Practices That Made Me Go 'Wow': What Every CNCF Project Can Learn From Envoy
26mMaking Envoy Sustainable
21mDeep Dive: Envoy
35mEnvoy Maintainer Q+A
33mThe End of a De...
17mLessons Learned: Four Years with Emissary-ingress and Envoy
