Envoy configuration control for code indexing routing
Problem to Solve
Once an Envoy gateway fronts the code indexing web servers, its routing rules must follow the state of the system: which instance owns which cache shard and which version it runs. Static routing configuration cannot keep up with rescheduling, scaling and rollouts.
Proposed Solution
- Give Orbit a way to change proxy routing at runtime, for example by writing Envoy Gateway routing resources or through an xDS control endpoint.
- Let Orbit control the sharding of the cache across web servers through these routing changes.
- Cover the routing updates with tests that confirm requests move with the shard.
Agent context — extended analysis, alternatives considered, related-code dumps
Source: item 10 of the "Scalable Code Indexing" section in Orbit GA Planning. Estimated size: 2 days. Depends on the Envoy gateway deployment issue.