Closed shuji-2019 closed 3 weeks ago
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
@shuji-2019 would https://github.com/envoyproxy/gateway/issues/3318 solve this use case ?
there may be multiple hostnames per hcm
For HTTP listeners on same port, will be translated to default_filter_chain
, each hostname to single VirtualHost
in same HCM
. It's not suitable to set all hostnames as stat_prefix
, maybe just contain http
and port
.
For HTTPS listeners on same port, will be translated to filter_chains
, each listener to single HCM
with SNI match own hostname (only one hostname). stat_prefix
can be set as hostname.
For TCP listeners (only single TCP listener is allowed on single port), will be translated to filter_chains
, each listener to single TCPProxy
with no match. stat_prefix
maybe contain tcp
and port
.
For TLS listeners on same port, will be translated to filter_chains
, each listener to single TCPProxy
with SNI match own hostname (only one hostname). stat_prefix
can be set as hostname.
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
can this be closed ?
can this be closed ?
It's fine to close this.
Description:
Because it's common to deploy many listeners for different domains, even serve multiple domains by single listener in which domains are distinguished via FilterChainMatch.SNI ^5. If all listeners share the same StatPrefix, it's difficult to tell how many traffic does specified domain have received. Consider sample from Envoy's
/stats/prometheus
.Relevant Links: