-
Notifications
You must be signed in to change notification settings - Fork 690
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
proxy to externalName service returns 503 #2873
Labels
lifecycle/accepted
Denotes an issue that has been triaged and determined to be valid.
Comments
youngnick
added
the
lifecycle/investigating
Denotes an issue that is assigned and is being actively investigated by the issue owner.
label
Sep 3, 2020
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 9, 2020
Adds the DnsLookupFamily: V4_ONLY to any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 16, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 16, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 17, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 17, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 18, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added
lifecycle/accepted
Denotes an issue that has been triaged and determined to be valid.
and removed
lifecycle/investigating
Denotes an issue that is assigned and is being actively investigated by the issue owner.
labels
Sep 18, 2020
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 18, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
to stevesloka/contour
that referenced
this issue
Sep 23, 2020
Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes projectcontour#2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
stevesloka
added a commit
that referenced
this issue
Sep 23, 2020
…rs (#2894) Adds a config option for DnsLookupFamily allowing users to define what dns lookup family is used on any cluster that is referenced via an externalName type cluster. This ensures that lookups to external resources are resolved correctly. Fixes #2873 Signed-off-by: Steve Sloka <slokas@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When configuring a route to an
externalName
service, requests don't get fulfilled properly, but return 503 errors. My first thought is that Envoy is not proxying when its DNS lookup returns an ipv6 address for the external resource.Below are some examples which recreate the issue. One thing to note is if you use my domain (e.g.
stevesloka.com
), it results in an ipv4 address and the proxy works just fine. My cluster is running in DigitalOcean proxying to a Node directly fronted with Contour.HTTPProxy:
Service:
Logs from Envoy:
//cc @brunopadz
The text was updated successfully, but these errors were encountered: