Adding feature documentation and task instructions for topology aware hints #1579
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… hints Signed-off-by: Alen Haric <alen@buoyant.io>
deusxanima
force-pushed
the
alen/topology-aware-hints
branch
from
3a430fc
to
73b5dcd
Compare
kflynn
requested changes
Mar 2, 2023
…mended by Flynn. Signed-off-by: Alen Haric <alen@buoyant.io>
Signed-off-by: Alen Haric <alen@buoyant.io>
Signed-off-by: Alen Haric <alen@buoyant.io>
kflynn
requested changes
May 5, 2023
| The main things to be aware of are: | ||
|
|
||
| - Linkerd assumes that traffic to a given zone will be roughly proportional to the capacity of the nodes in the zone (which can be a concern when using horizontal pod autoscaling, as the HPA may start nodes in the "wrong" zone); and | ||
| - The Kubernetes endpoint slice controller does not take... |
| ] | ||
| +++ | ||
|
|
||
| Kuberentes clusters are increasingly deployed in multi-zone environments with network traffic often relying on obscure endpoint matching and routing for a given service. Linkerd's implementation of Kubernetes ([Topology Aware Hints][topology aware hints]) provides users with a mechanism for asserting more control over endpoint selection and routing within a cluster that spans multiple zones. Users can now implement routing constraints and prefer endpoints in a specific zone in order to limit cross-zone networking costs or improve performance through lowered cross-zone latency and bandwidth constraints. |
There was a problem hiding this comment.
s/Kuberentes/Kubernetes/ (or, better, just directly copy all your 2.12 docs to 2.13?)
|
what's holding this back? 😃 |
|
We still need some corrections to it, and it looks like @deusxanima is out this week. I'll see if I can't get things moving to bring it in soon, though. |
|
any news? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem: topology aware hints feature implementation is not currently documented on linkerd.io
Solution: adding feature documentation and task instructions for topology aware hints
Fixes: #1519
Signed-off-by: Alen Haric alen@buoyant.io