Pole Sidecar as a lightweight data plane
Why Pingora sits beside apps, and how it shares facts with the control plane.
Pole Sidecar uses Pingora so multi-language services can still consume Lattice Hub discovery and governance without embedding every SDK.
Positioning
- Local execution: HTTP/gRPC forward, route match, LB, interceptor hooks.
- Control plane owns facts: services, config, and active governance releases.
- Coexists with SDKs: Rust can stay proxyless; other languages can use Sidecar.
Current skeleton
- TOML routes and upstream clusters
grpc_prefixbeforeprefix- Sample round-robin LB
- Request/upstream interceptor placeholders
Next
Wire interceptors to real limiting, breaking, auth, and metrics, and pair with Controller dns / mesh injection. Before that, close the loop on forward, observe, and align with control-plane versions.