Skip to content
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

internal/envoy: use strict DNS for resolving the cluster #238

Merged
merged 1 commit into from
Feb 15, 2018

Conversation

sevein
Copy link
Contributor

@sevein sevein commented Feb 12, 2018

Fixes #228.

This enable us to define the contour cluster as a DNS name. I have confirmed
that STRICT_DNS also works when the address is an IP.

As mentioned by @davecheney before, with #158 and #228 fixed we should be able
to split Contour and Envoy into separate pods. Proof of concept:
https://gist.github.com/sevein/d30e1791fbc0db786884360486e70737.

Signed-off-by: Jesús García Crespo jesus@sevein.com

Fixes projectcontour#228.

This enable us to define the contour cluster as a DNS name. I have confirmed
that `STRICT_DNS` also works when the address is an IP.

As mentioned by @davecheney before, with projectcontour#158 and projectcontour#228 fixed we should be able
to split Contour and Envoy into separate pods. Proof of concept:
https://gist.github.com/sevein/d30e1791fbc0db786884360486e70737.

Signed-off-by: Jesús García Crespo <jesus@sevein.com>
@davecheney davecheney merged commit f1b1bac into projectcontour:master Feb 15, 2018
@sevein sevein deleted the xds-cluster-dns branch February 15, 2018 18:19
sunjayBhatia pushed a commit that referenced this pull request Jan 30, 2023
Signed-off-by: Daneyon Hansen <daneyonhansen@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Find a way to allow xds_cluster to be defined as a DNS name, not an IP address
2 participants