Support Topology Aware Hint
- Dominant language
- Go
- Stars
- 6.1k
- Forks
- 1.2k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 2
Description
## What is changing? (Please include as many details as possible.)
The address that Knative registers in Revision's EndpointSlice does not include zone information.
Can we include zone information to optimize traffic routing?
https://kubernetes.io/docs/concepts/services-networking/topology-aware-hints/#implementation-control-plane
## How will this impact our users?
## In what release will this take happen (to the best of your knowledge)?
Ex. v0.2-v0.3
## Context
None
## Additional info
Contributor guide
Research direction
Start with the Revision EndpointSlice address-registration path and read the linked Kubernetes topology-aware hints implementation-control-plane documentation. Determine how zone information should be supplied, then verify that registered EndpointSlices include it and that the relevant routing behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100