xds configs, outbound listeners should use the clustername instead of an IP/port combo #12093
Labels
Comments
johncowen
added
kind/bug
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
For example, here I have an outbound with an obscure ip, and it would be better to use the name of the cluster ie:
outbound:10.43.205.116:6379vsoutbound:default_redis_kuma-demo_default_msvc_6379Lmk if there is any reason why this isn't possible 👍
{ "name": "outbound:10.43.205.116:6379", "active_state": { "version_info": "bd1b34d7-f8e7-4605-82c0-f97ac2b06f27", "listener": { "@type": "type.googleapis.com/envoy.config.listener.v3.Listener", "name": "outbound:10.43.205.116:6379", "address": { "socket_address": { "address": "10.43.205.116", "port_value": 6379 } }, "filter_chains": [ { "filters": [ { "name": "envoy.filters.network.tcp_proxy", "typed_config": { "@type": "type.googleapis.com/envoy.extensions.filters.network.tcp_proxy.v3.TcpProxy", "stat_prefix": "default_redis_kuma-demo_default_msvc_6379", "cluster": "default_redis_kuma-demo_default_msvc_6379", "max_connect_attempts": 5, "idle_timeout": "3600s" } } ] } ], "metadata": { "filter_metadata": { "io.kuma.tags": {} } }, "traffic_direction": "OUTBOUND", "bind_to_port": false }, "last_updated": "2024-11-14T12:12:36.233Z" } },The text was updated successfully, but these errors were encountered: