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

when Cluster using EDS service to fectch endpoints ,can't using DNS name in endpoint address #4290

Closed
leader-us opened this issue Aug 29, 2018 · 6 comments
Assignees
Labels
no stalebot Disables stalebot from closing an issue question Questions that are neither investigations, bugs, nor enhancements

Comments

@leader-us
Copy link

when Cluster using EDS to fetch endpionts ,I can't using DNS names in endpoint address ,

resource_names: "test-cluster"
type_url: "type.googleapis.com/envoy.api.v2.ClusterLoadAssignment"
response_nonce: "2705"
error_detail {
code: 13
message: "Unknown address resolver: service1. Consider setting resolver_name or setting cluster type to 'STRICT_DNS' or 'LOGICAL_DNS'"
}

is there any choise ?

@dio
Copy link
Member

dio commented Aug 29, 2018

@leader-us you can either resolve the domain in your management server or do complete CDS response.

Related: envoyproxy/go-control-plane#87 (comment)

@leader-us
Copy link
Author

Thanks,May be support DNS name in EDS endpoints will better

@dio
Copy link
Member

dio commented Aug 30, 2018

@leader-us yes true. We hope we can support it eventually. PR is welcome.

@lizan lizan added the question Questions that are neither investigations, bugs, nor enhancements label Aug 30, 2018
@stale
Copy link

stale bot commented Sep 29, 2018

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Sep 29, 2018
@stale
Copy link

stale bot commented Oct 6, 2018

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@techpavan
Copy link

Looks like this is still open. Can someone please confirm if so?

@phlax phlax added no stalebot Disables stalebot from closing an issue and removed stale stalebot believes this issue/PR has not been touched recently labels Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no stalebot Disables stalebot from closing an issue question Questions that are neither investigations, bugs, nor enhancements
Projects
None yet
Development

No branches or pull requests

6 participants