Enhancement freeze exception request - KEP 1860 - Make Kubernetes aware of the LoadBalancer behaviour

[Ricardo Katz]

Hi all,

I would like to request an exception on feature freeze for KEP 1860 -
Make Kubernetes aware of the LoadBalancer behaviour, and opt-in on it
for v1.30 to be promoted to Beta. The feature risk is low and very
specific to Cloud Providers and a specific situation (CCM should set a
status field on a service resource that will change for that service
how service proxy should program network interfaces and/or NAT rules).

The KEP is already approved by both SIG Leads (thanks Dan Winship!),
PRR reviews (thanks Wojtek!) and merged, targeting v1.30.

Thanks!
=======
Enhancement name: Make Kubernetes aware of the LoadBalancer behaviour
Enhancement status (alpha/beta/stable): beta
SIG: network
k/enhancements repo issue #: #1860
PR #’s: https://github.com/kubernetes/enhancements/pull/4509 (already
approved by SIG and PRR reviewer and merged)
Additional time needed (in days): 1 (PR for KEP is already merged)
Reason this enhancement is critical for this milestone: No reason, but
it is a bare simple enhancement that fell out of the radar
Risks from adding code late: (to k8s stability, testing, etc.): low
risk, the enhancement touches a very specific part of kube-proxy, not
adding the LoadBalancer IP to the "rules" anymore in case a new status
API field, set by a LoadBalancer controller, changes the default value
Risks from cutting enhancement: (partial implementation, critical
customer usecase, etc.): critical for cloud providers that rely on the
new behavior to do proper load balancing

[Kat Cosgrove]

Hi all,

Following discussion in Slack, the release team is APPROVING this exception request. Your updated deadline to merge all open code implementation PRs and docs for your KEP is 18:00 PST Tuesday, 21st February 2024.

If you need any clarification, please reach out to us in the #sig-release Slack channel.

Thanks,
Kat Cosgrove
1.30 Release Team Lead

--
To unsubscribe from this group and stop receiving emails from it, send an email to release-team...@kubernetes.io.