You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cross-AZ traffic is very expensive at scale between Loki, Mimir and Tempo components in our EKS cluster.
Which solution do you envision (roughly)?
K8s 1.31 includes a trafficDistribution feature where you can set PreferClose so that topologically requests on services can jump to the nearest pod, this can mean requests remain even on the same node rather than incurring expensive cross availability zone traffic costs in AWS or other cloud providers.
Have you considered any alternatives?
No response
Any additional context to share?
No response
How long do you think this would take to be developed?
Small (<= 1 month dev)
What are the documentation dependencies?
No response
Proposer?
No response
The text was updated successfully, but these errors were encountered:
What is the problem you are trying to solve?
Cross-AZ traffic is very expensive at scale between Loki, Mimir and Tempo components in our EKS cluster.
Which solution do you envision (roughly)?
K8s 1.31 includes a trafficDistribution feature where you can set PreferClose so that topologically requests on services can jump to the nearest pod, this can mean requests remain even on the same node rather than incurring expensive cross availability zone traffic costs in AWS or other cloud providers.
Have you considered any alternatives?
No response
Any additional context to share?
No response
How long do you think this would take to be developed?
Small (<= 1 month dev)
What are the documentation dependencies?
No response
Proposer?
No response
The text was updated successfully, but these errors were encountered: