Make Kubernetes aware of the LoadBalancer behaviour

[Sh4d1]

Enhancement Description

• Make Kubernetes aware of the LoadBalancer behaviour
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/1860-kube-proxy-IP-node-binding
• Primary contact (assignee): @Sh4d1 @rikatz @RyanAoh
• Responsible SIGs: sig-network, sig-cloudprovider
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.29
  • Beta release target (x.y): 1.30
  • Stable release target (x.y): 1.32
• Alpha
  • KEP (k/enhancements) update PR(s):
    • 1.19 Make Kubernetes aware of the LoadBalancer behaviour #1392
    • 1.20 Set KEP 1860 as implementable #2134
    • 1.29 KEP-1860: Make Kubernetes aware of the LoadBalancer behavior (reopen) #4114
  • Code (k/k) update PR(s):
    • 1.28 Make Kubernetes aware of the LoadBalancer behaviour kubernetes#118895
    • Make Kubernetes aware of the LoadBalancer behaviour kubernetes#119937
    • follow up on " Merged Make Kubernetes aware of the LoadBalancer behaviour" kubernetes#120068
  • Docs (k/website) update(s):
    • add blog for feature LoadBalancerIPMode website#43904
    • add doc for feature LoadBalancerIPMode website#43476
• Beta
  • KEP (k/enhancements) update PR(s): KEP-1860 - Propose beta graduation and add missing PRR  #4509
  • Code (k/k) update PR(s): Promote LoadBalancerIPMode to Beta kubernetes#123418
  • Docs (k/website) update(s): Promote LoadBalancerIPMode to Beta website#45219
• Stable
  • KEP (k/enhancements) update PR(s): Add the implementation history section #4891, Promote LoadBalancerIPMode to GA #4854
  • Code (k/k) update PR(s): Promote LoadBalancerIPMode to GA kubernetes#127348
  • Docs (k/website) update(s): Promote LoadBalancerIPMode to GA website#47938

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

[Sh4d1]

/sig network

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[Sh4d1]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @Sh4d1

1.20 Enhancements Lead here. This KEP still seems to be a draft (it's provisional) but wanted to check-in to see if you thought this would be graduating alpha in 1.20?

Enhancements Freeze is October 6th and by that time we require:

The KEP must be merged in an implementable state
The KEP must have test plans
The KEP must have graduation criteria
The KEP must have an issue in the milestone

Best,
Kirsten

[kikisdeliveryservice]

Note: this provisional kep was implemented without having a compliant kep or indicating to the enhancements team that it would be in the 1.20 milestone.

[jeremyrickard]

Hey @Sh4d1 and @thockin,

👋 1.20 release lead here. We're really close to code freeze at this point (Thursday) and it seems like this KEP fell through the cracks and the process.

Based on this comment in the PR above: kubernetes/kubernetes#92312 (comment) can we not land this in 1.20 and instead target 1.21?

There are few things w/ the KEP that really should be address:

• It's provisional still
• There is no test plan
• There is no graduation criteria

Looks like there is also a PR to update the KEP https://github.com/kubernetes/enhancements/pull/2134/files that addresses this stuff, however it also marks it as implemented and targets 1.21. Typically, we set to implemented only after the release.

Can we circle back around on this and agree that we should try to land this in 1.21 at this point? We've already got a lot of content for the release so far (sig-docs has their work cut out for themselves!!!), we're two days out from code freeze, we have these disconnects mentioned above?