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

Service Topology #4325

Closed
grampelberg opened this issue May 1, 2020 · 1 comment
Closed

Service Topology #4325

grampelberg opened this issue May 1, 2020 · 1 comment
Labels
area/cli area/controller area/proxy gsoc rfc

Comments

@grampelberg
Copy link
Contributor

What problem are you trying to solve?

It is valuable to have metadata related to the topology of a cluster when making load balancing decisions. This metadata can be used to control egress costs between regions or even make advanced routing decisions in multicluster situations. As part of Kubernetes 1.17, service topology landed. This provides extra metadata as part of endpoints for a service to control weighting. Imagine transparently failing over to nodes running in a different zone if the pods locally are no longer running. Linkerd should implement support for this functionality.
@mateiidavid mateiidavid mentioned this issue May 11, 2020
Closed
@grampelberg
Copy link
Contributor Author

Done!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
area/cli area/controller area/proxy gsoc rfc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grampelberg