You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing [email protected] where the issue will be triaged appropriately.
Title: DNS does not find docker containers in same network
Description:
I updated from envoyproxy/envoy-distroless:v1.31.5 to envoyproxy/envoy-distroless:v1.32.3 and now envoy does not resolve other docker containers in the same network anymore.
I enabled some logs and see the following:
[2025-01-15 10:48:49.504][28][debug][router] [source/common/router/router.cc:527] [Tags: "ConnectionId":"0","StreamId":"5305907000402733376"] cluster 'ext-authz' match for URL '/envoy.service.auth.v3.Authorization/Check'
[2025-01-15 10:48:49.505][28][debug][connection] [source/common/network/connection_impl.cc:1017] [Tags: "ConnectionId":"2"] connecting to <ip>:80
If I start envoy 1.31 the IP is the IP of my extauthz container in the docker network. Envoy 1.32 probably queries not the docker network resolver but my host resolver and gets a wrong IP. I would expect envoy to resolve the IP of the container.
Other clusters have the same problem, if I change to type: static everything works.
Names like auth.example.com get resolved correctly too.
Repro steps:
A simple gRPC request that matches /my.prefix/ and is forwarded to ext authz triggers this
Note: The Envoy_collect tool
gathers a tarball with debug logs, config and the following admin
endpoints: /stats, /clusters and /server_info. Please note if there are
privacy concerns, sanitize the data prior to sharing the tarball/pasting.
Admin and Stats Output:
Include the admin output for the following endpoints: /stats,
/clusters, /routes, /server_info. For more information, refer to the admin endpoint documentation.
Note: If there are privacy concerns, sanitize the data prior to
sharing.
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
[email protected] where the issue will be triaged appropriately.
Title: DNS does not find docker containers in same network
Description:
I updated from
envoyproxy/envoy-distroless:v1.31.5
toenvoyproxy/envoy-distroless:v1.32.3
and now envoy does not resolve other docker containers in the same network anymore.I enabled some logs and see the following:
If I start envoy 1.31 the IP is the IP of my extauthz container in the docker network. Envoy 1.32 probably queries not the docker network resolver but my host resolver and gets a wrong IP. I would expect envoy to resolve the IP of the container.
Other clusters have the same problem, if I change to
type: static
everything works.Names like
auth.example.com
get resolved correctly too.Repro steps:
A simple gRPC request that matches
/my.prefix/
and is forwarded to ext authz triggers thisAdmin and Stats Output:
Config:
Logs:
The text was updated successfully, but these errors were encountered: