5 ms·
You don't call Envoy to make changes. You either update the config file, or you implement an API server with a specific set of endpoints, then have it serve the
by trjordan 9y ago
You don't call Envoy to make changes. You either update the config file, or you implement an API server with a specific set of endpoints, then have it serve the updated values back. It's a bit tricky, but entirely doable. https://envoyproxy.github.io/envoy/intro/arch_overview/dynamic_configuration.html https://envoyproxy.github.io/envoy/intro/arch_overview/dynam...
(You can do this in nginx, too, and it's similarly annoying. This is a big part of what we do at Turbine Labs -- a UI with a slider between blue and green, and a place to host all those stats, so you don't have to manage it!)
- nailer 9y agoI'd use Houston in a heartbeat over nginx (currently flying blind, but need it for HTTP/2) but it's hard to compete with free. It's hard to read what your licensing/support model is like without signing up. Considered a Red Hat like support model?