PreferSameNode Traffic Distribution (formerly PreferLocal traffic policy / Node-level topology)

[danwinship]

PerferSameNode Traffic Distribution (formerly Node-level topology (formerly PreferLocal traffic policy))

• One-line enhancement description (can be used as a release note):
  Add a way to signal to kube-proxy that it should deliver traffic to a local endpoint whenever possible, for efficiency.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/3015-prefer-same-node
• Discussion Link: KEP-2086: Add internalTrafficPolicy: PreferLocal #3010, KEP-3015: PreferLocal traffic policy #3016, KEP-4444: add "prefer same node" semantics to PreferClose #4931
• Primary contact (assignee): @danwinship
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.33
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.35
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-3015: PreferSameZone/PreferSameNode traffic distribution #5140
  • Code (k/k) update PR(s):
    • KEP-3015 PreferSameZone/PreferSameNode traffic distribution kubernetes#130844
    • integration testing for PreferSameZone/PreferSameNode kubernetes#130944
    • e2e testing for PreferSameZone/PreferSameNode kubernetes#130945
  • Docs (k/website) update PR(s): KEP-3015 PreferSameNode TrafficDistribution 1.33 website#49943
• Beta
  • KEP (k/enhancements) update PR(s): KEP-3015: PreferSameZone/PreferSameNode to beta #5376
  • Code (k/k) update PR(s): KEP-3015: PreferSameTrafficDistribution to Beta kubernetes#132127
  • Docs (k/website) update(s): KEP-3015: PreferSameTrafficDistribution to Beta website#51185
• Stable
  • KEP (k/enhancements) update PR(s): KEP-3015: update PreferSame* TrafficDistribution to GA #5567
  • Code (k/k) update PR(s): KEP-3015: update PreferSameTrafficDistribution to GA kubernetes#134457
  • Docs (k/website) update(s): KEP-3015: Update PreferSameTrafficDistribution to GA website#52650

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[danwinship]

/sig network

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[danwinship]

/remove-lifecycle stale

[danwinship]

Given the discussion on #3016 I think we want to drop this from 1.24 but keep it open (for now)