1
- # KEP-20190603 EndpointSlices
1
+ # KEP-0752 EndpointSlices
2
2
3
3
## Table of Contents
4
4
41
41
- [ E2E Tests] ( #e2e-tests )
42
42
- [ Roll Out Plan] ( #roll-out-plan )
43
43
- [ Graduation Criteria] ( #graduation-criteria )
44
+ - [ Alpha -> ; Beta] ( #alpha---beta )
45
+ - [ Beta -> ; GA] ( #beta---ga )
44
46
- [ Splitting IP address type for better dual stack support] ( #splitting-ip-address-type-for-better-dual-stack-support )
45
47
- [ Production Readiness Review Questionnaire] ( #production-readiness-review-questionnaire )
46
48
- [ Feature enablement and rollback] ( #feature-enablement-and-rollback )
@@ -647,7 +649,7 @@ The following will need to be covered as part of the testing plan:
647
649
648
650
## Graduation Criteria
649
651
650
- In order to graduate to beta, we will:
652
+ ### Alpha -> Beta
651
653
652
654
- Kube-proxy switch to consume EndpointSlice API. (Already done in Alpha)
653
655
- Verify performance/scalability via testing. (Scale tested to 50k endpoints in
@@ -660,6 +662,13 @@ In order to graduate to beta, we will:
660
662
- Add FQDN addressType.
661
663
- Add support for optional appProtocol field on ` EndpointPort ` .
662
664
665
+ ### Beta -> GA
666
+
667
+ - EndpointSlice API has been stable at beta for at least 2 minor releases.
668
+ - EndpointSlice Controller has been enabled by default for 2 minor releases.
669
+ - EndpointSlices has been used by default for at least 1 minor release.
670
+ - Implementation has been scaled tested beyond 100k endpoints.
671
+
663
672
### Splitting IP address type for better dual stack support
664
673
665
674
Although the initial vision for the ` IP ` address type was to be inclusive of
0 commit comments