-
Notifications
You must be signed in to change notification settings - Fork 712
Unable to route to FQDN EndpointSlice when using TLSRoute #2832
Copy link
Copy link
Closed
Description
Description:
What issue is being seen? Describe what should be happening instead of
the bug, for example: Envoy should not crash, the expected value isn't
returned, etc.
Unable to route, seeing errors in Envoy
[2024-03-08 02:38:43.755][1][warning][main] [source/server/server.cc:925] There is no configured limit to the number of allowed active downstream connections. Configure a limit in `envoy.resource_monitors.downstream_connections` resource monitor.
[2024-03-08 02:41:40.372][1][warning][config] [source/extensions/config_subscription/grpc/delta_subscription_state.cc:269] delta config for type.googleapis.com/envoy.config.endpoint.v3.ClusterLoadAssignment rejected: malformed IP address: httpbin.org. Consider setting resolver_name or setting cluster type to 'STRICT_DNS' or 'LOGICAL_DNS'
[2024-03-08 02:41:40.372][1][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:138] gRPC config for type.googleapis.com/envoy.config.endpoint.v3.ClusterLoadAssignment rejected: malformed IP address: httpbin.org. Consider setting resolver_name or setting cluster type to 'STRICT_DNS' or 'LOGICAL_DNS'
[2024-03-08 02:41:40.372][1][warning][config] [source/extensions/config_subscription/grpc/grpc_subscription_impl.cc:138] gRPC config for type.googleapis.com/envoy.config.endpoint.v3.ClusterLoadAssignment rejected: malformed IP address: httpbin.org. Consider setting resolver_name or setting cluster type to 'STRICT_DNS' or 'LOGICAL_DNS'
{"start_time":"2024-03-08T02:42:06.176Z","method":"-","x-envoy-origin-path":"-","protocol":"-","response_code":"0","response_flags":"UH","response_code_details":"-","connection_termination_details":"-","upstream_transport_failure_reason":"-","bytes_received":"0","bytes_sent":"0","duration":"0","x-envoy-upstream-service-time":"-","x-forwarded-for":"-","user-agent":"-","x-request-id":"-",":authority":"-","upstream_host":"-","upstream_cluster":"tlsroute/default/httpbin/rule/-1","upstream_local_address":"-","downstream_local_address":"10.1.10.196:10443","downstream_remote_address":"192.168.65.4:34028","requested_server_name":"-","route_name":"-"}
Repro steps:
Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.
Follow steps outlined in doc In #2831
Note: If there are privacy concerns, sanitize the data prior to
sharing.
Environment:
Include the environment like gateway version, envoy version and so on.
Logs:
Include the access logs and the Envoy logs.
Reactions are currently unavailable