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.

Sign up for GitHub

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

Jump to bottom

Multi-Cluster: Can only reach local Headless service #27342

Closed
stevenctl opened this issue Sep 16, 2020 · 1 comment · Fixed by #32515
Closed

Multi-Cluster: Can only reach local Headless service #27342

stevenctl opened this issue Sep 16, 2020 · 1 comment · Fixed by #32515
Assignees
@stevenctl
Labels
area/networking feature/Multi-cluster issues related with multi-cluster support kind/test failure lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically.

Comments

@stevenctl
Copy link
Contributor

stevenctl commented Sep 16, 2020 •
edited
Loading

With in-agent DNS, we should be able to support headless services having multiple IPs.

For headless Services that define selectors, the endpoints controller creates Endpoints records in the API, and modifies the DNS configuration to return records (addresses) that point directly to the Pods backing the Service.
@stevenctl stevenctl added kind/test failure feature/Multi-cluster issues related with multi-cluster support labels Sep 16, 2020
@stevenctl stevenctl self-assigned this Sep 16, 2020
@stevenctl stevenctl mentioned this issue Sep 16, 2020
Merged
@stevenctl stevenctl changed the title headless services don't work with multicluster Multi-Cluster: Can only reach local Headless service Sep 29, 2020
@istio-policy-bot istio-policy-bot added the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Dec 15, 2020
@istio-policy-bot istio-policy-bot added the lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. label Dec 30, 2020
@stevenctl stevenctl mentioned this issue Jan 14, 2021
Closed
@stevenctl
Copy link
Contributor Author

stevenctl commented Mar 18, 2021 •
edited
Loading

Headless services do not work. In a single network, we send directly to the pod's IP using ORIGINAL_DST. When we do ORIGINAL_DST, we never get redirected to the gateway. Even if we did get redirected to the gateway, once we got there we have no way to route to the intended destination.

@stevenctl stevenctl reopened this Mar 18, 2021
@istio-policy-bot istio-policy-bot removed the lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while label Mar 18, 2021
@stevenctl stevenctl mentioned this issue Apr 19, 2021
Open
31 tasks
@stevenctl stevenctl mentioned this issue Apr 28, 2021
Merged
@stevenctl stevenctl mentioned this issue Aug 9, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stevenctl stevenctl

Labels
area/networking feature/Multi-cluster issues related with multi-cluster support kind/test failure lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

allow resolving same-network cross-cluster headless services stevenctl/istio
3 participants
@howardjohn @stevenctl @istio-policy-bot