Running Envoy at the Edge
summary
Pinterest migrates its edge from varnish to Envoy and reaches 100% of edge LB by summer, running Envoy in Docker with hot restart and a zookeeper-backed sidecar control plane that emits EDS and a route map. Engineers add a header-to-metadata filter, CDN HMAC request signing, bot-detection and access filters, and a staged-deploy route-map that pins users; subset load balancing plus a few hundred lines of glue code does the routing. Fixes include raising default circuit-breakers (1024 caused ~1k RPS cap vs varnish 6–7k) and health check coalescing to stop an 86% CPU hot loop.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 0:46Our Stack
- 1:24Why Migrating
- 5:34Features
- 7:12Migration hiccups
- 9:44Deploys
- 10:21Versions
- 10:56Route Versions
- 11:10Header to metadata filter
- 11:24CPU usage
- 13:07Health Check Coalescing
- 13:43AP Deploy
- 14:22Constraints
- 14:37Staging Deploys
- 16:00Filtering
- 17:03Interfaces
- 17:48Custom Solution
- 18:26Problem Favorite
- 18:39Favorite Feature
- 19:07Observability
- 19:32The future
- 20:28Questions
related talks
26mIntegrating Stateful Load Balancing At Scale In Envoy
10mLightning Talk: Envoy @ Netflix
06mLivin' on the Edge (of your cluster)
11mEnvoy Namespaces - Operating an Envoy-based Service Mesh at a Fraction of the Cost
25mBuilding Low Latency Topologies with Envoy
10mUsing VPP as Envoy's Network Stack
36mFine Grained Mesh Metrics for Better Visibility With Native Performance
28mSmall Changes, Big Results