Skip to content

Commit d723d19

Browse files
committed
KEP-3015: update PreferSame* TrafficDistribution to GA
1 parent cebf304 commit d723d19

File tree

3 files changed

+5
-46
lines changed

3 files changed

+5
-46
lines changed

keps/prod-readiness/sig-network/3015.yaml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,5 @@ alpha:
66
approver: "@wojtek-t"
77
beta:
88
approver: "@wojtek-t"
9+
stable:
10+
approver: "@wojtek-t"

keps/sig-network/3015-prefer-same-node/README.md

Lines changed: 0 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
# KEP-3015 PreferSameZone and PreferSameNode Traffic Distribution
22

33
<!-- toc -->
4-
- [Release Signoff Checklist](#release-signoff-checklist)
54
- [Summary](#summary)
65
- [Motivation](#motivation)
76
- [Goals](#goals)
@@ -37,48 +36,6 @@
3736
- [Alternatives](#alternatives)
3837
<!-- /toc -->
3938

40-
## Release Signoff Checklist
41-
42-
<!--
43-
**ACTION REQUIRED:** In order to merge code into a release, there must be an
44-
issue in [kubernetes/enhancements] referencing this KEP and targeting a release
45-
milestone **before the [Enhancement Freeze](https://git.k8s.io/sig-release/releases)
46-
of the targeted release**.
47-
48-
For enhancements that make changes to code or processes/procedures in core
49-
Kubernetes—i.e., [kubernetes/kubernetes], we require the following Release
50-
Signoff checklist to be completed.
51-
52-
Check these off as they are completed for the Release Team to track. These
53-
checklist items _must_ be updated for the enhancement to be released.
54-
-->
55-
56-
Items marked with (R) are required *prior to targeting to a milestone / release*.
57-
58-
- [X] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
59-
- [X] (R) KEP approvers have approved the KEP status as `implementable`
60-
- [X] (R) Design details are appropriately documented
61-
- [X] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
62-
- [X] e2e Tests for all Beta API Operations (endpoints)
63-
- [ ] (R) Ensure GA e2e tests meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
64-
- [ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
65-
- [X] (R) Graduation criteria is in place
66-
- [X] (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)
67-
- [X] (R) Production readiness review completed
68-
- [X] (R) Production readiness review approved
69-
- [X] "Implementation History" section is up-to-date for milestone
70-
- [X] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
71-
- [X] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
72-
73-
<!--
74-
**Note:** This checklist is iterative and should be reviewed and updated every time this enhancement is being considered for a milestone.
75-
-->
76-
77-
[kubernetes.io]: https://kubernetes.io/
78-
[kubernetes/enhancements]: https://git.k8s.io/enhancements
79-
[kubernetes/kubernetes]: https://git.k8s.io/kubernetes
80-
[kubernetes/website]: https://git.k8s.io/website
81-
8239
## Summary
8340

8441
Discussion about trying to add "prefer same node" behavior to

keps/sig-network/3015-prefer-same-node/kep.yaml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ authors:
44
- "@danwinship"
55
owning-sig: sig-network
66
participating-sigs:
7-
status: implementable
7+
status: implemented
88
creation-date: 2025-01-23
99
reviewers:
1010
- "@gauravkghildiyal"
@@ -17,12 +17,12 @@ see-also:
1717
replaces:
1818

1919
# The target maturity stage in the current dev cycle for this KEP.
20-
stage: beta
20+
stage: stable
2121

2222
# The most recent milestone for which work toward delivery of this KEP has been
2323
# done. This can be the current (upcoming) milestone, if it is being actively
2424
# worked on.
25-
latest-milestone: "v1.34"
25+
latest-milestone: "v1.35"
2626

2727
# The milestone at which this feature was, or is targeted to be, at each stage.
2828
milestone:

0 commit comments

Comments
 (0)