Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the implementation history section #4891

Merged
merged 1 commit into from
Oct 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion keps/sig-network/1860-kube-proxy-IP-node-binding/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,7 @@
- [Dependencies](#dependencies)
- [Scalability](#scalability)
- [Troubleshooting](#troubleshooting)
- [Implementation History](#implementation-history)
<!-- /toc -->

## Release Signoff Checklist
Expand Down Expand Up @@ -134,9 +135,13 @@ Unit tests:
- unit tests for the ipvs and iptables rules
- unit tests for the validation

Integration tests:
- https://github.com/kubernetes/kubernetes/pull/125237

E2E tests:
- The default behavior for `ipMode` does not break any existing e2e tests
- The default `VIP` value is already tested
- https://github.com/kubernetes/kubernetes/pull/124876

## Graduation Criteria

Expand Down Expand Up @@ -377,4 +382,10 @@ kube-proxy reacts on the IP status, so the service LoadBalancer IP and configura
N/A

###### What steps should be taken if SLOs are not being met to determine the problem?
N/A
N/A

## Implementation History

- 2020-06-18: Initial KEP
- 2023-12-14: Alpha release with Kubernetes 1.29
- 2024-04-18: Beta release with Kubernetes 1.30