-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1.32 DNS Regression #38016
Comments
@trivialkettle Could you try explicitly passing in the resolver address using typed_dns_resolver_config? |
@agrawroh thanks for the answer. I played around with At the end I solved it passing
to the envoy service in my |
I had the same issue when deploying the OpenTelemetry Demo. Setting |
Had the same issue: search domain being |
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: