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

Adding feature documentation and task instructions for topology aware hints #1579

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

deusxanima
Copy link

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 [email protected]

Copy link
Member

@kflynn kflynn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a bunch of comments with little copyediting things -- overall, I really like having this content, many thanks!! 🙂

Copy link
Member

@kflynn kflynn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Still found a coupla things that need a bit of attention. 🙂

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...
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

...does not take what?

]
+++

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/Kuberentes/Kubernetes/ (or, better, just directly copy all your 2.12 docs to 2.13?)

@tuxillo
Copy link

tuxillo commented Jan 2, 2024

what's holding this back? 😃

@kflynn
Copy link
Member

kflynn commented Jan 3, 2024

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.

@tuxillo
Copy link

tuxillo commented Apr 14, 2024

any news?

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.

Document how to use topology aware hints with Linkerd
3 participants