Merge pull request #5240 from danwinship/kep-1860-implemented

KEP-1860: mark as implemented

Author: k8s-ci-robot

keps/sig-network/1860-kube-proxy-IP-node-binding/README.md

@@ -3,7 +3,6 @@
 ## Table of Contents
 
 <!-- toc -->
-- [Release Signoff Checklist](#release-signoff-checklist)
 - [Summary](#summary)
 - [Motivation](#motivation)
   - [Goals](#goals)
@@ -33,26 +32,6 @@
 - [Implementation History](#implementation-history)
 <!-- /toc -->
 
-## Release Signoff Checklist
-
-Items marked with (R) are required *prior to targeting to a milestone / release*.
-
-- [x] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
-- [x] (R) KEP approvers have approved the KEP status as `implementable`
-- [x] (R) Design details are appropriately documented
-- [ ] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
-  - [ ] e2e Tests for all Beta API Operations (endpoints)
-  - [ ] (R) Ensure GA e2e tests meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
-  - [ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
-- [ ] (R) Graduation criteria is in place
-  - [ ] (R) [all GA Endpoints](https://github.com/kubernetes/community/pull/1806) must be hit by [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
-- [ ] (R) Production readiness review completed
-- [ ] (R) Production readiness review approved
-- [ ] "Implementation History" section is up-to-date for milestone
-- [ ] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
-- [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
-
-
 ## Summary
 
 The different kube-proxy implementations (at least ipvs and iptables), as of today, are binding the External IPs of the LoadBalancer Service to each node. (iptables are creating some rules to redirect packets directly to the service and ipvs is binding the IP to one interface on the node). This feature exists because:
@@ -388,4 +367,5 @@ N/A
 
 - 2020-06-18: Initial KEP
 - 2023-12-14: Alpha release with Kubernetes 1.29
-- 2024-04-18: Beta release with Kubernetes 1.30
+- 2024-04-18: Beta release with Kubernetes 1.30
+- 2024-12-11: GA release with Kubernetes 1.32

keps/sig-network/1860-kube-proxy-IP-node-binding/kep.yaml

@@ -5,7 +5,7 @@ authors:
 owning-sig: sig-network
 participating-sigs:
   - sig-cloud-provider
-status: implementable
+status: implemented
 reviewers:
   - "@thockin"
   - "@cheftako"