Conversation
This isn't something we want to expose when running Envoy Mobile. For more details: envoyproxy/envoy#21814 Signed-off-by: JP Simard <jp@jpsim.com>
|
How does this work with |
I was only vaguely aware of this configuration point. I didn't know that the html interface was what we were explicitly exposing. Knowing that this is an explicitly enabled feature changes the discussion on this for sure. I had started a discussion on Slack here: https://envoyproxy.slack.com/archives/C02F93EEJCE/p1656350561377359
Yes that's my understanding as well based on the description in envoyproxy/envoy#21814. |
The feature was about exposing |
|
This should be good to merge no? |
|
No, we decided to keep the feature enabled in our last community meeting, but to eventually replace it with safer programmatic APIs to provide the same kind of debugging features. |
This isn't something we want to expose when running Envoy Mobile.
For more details: envoyproxy/envoy#21814
Risk Level: Low, will impact anyone who's used this feature before.
Testing: Verified that
admin_html.ccis not compiled.Docs Changes: N/A
Release Notes: N/A