You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Feature Enablement and Rollback](#feature-enablement-and-rollback)
25
26
-[Rollout, Upgrade and Rollback Planning](#rollout-upgrade-and-rollback-planning)
@@ -38,20 +39,20 @@
38
39
39
40
Items marked with (R) are required _prior to targeting to a milestone / release_.
40
41
41
-
-[] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
42
-
-[] (R) KEP approvers have approved the KEP status as `implementable`
43
-
-[] (R) Design details are appropriately documented
44
-
-[] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
45
-
-[] e2e Tests for all Beta API Operations (endpoints)
46
-
-[] (R) Ensure GA e2e tests for meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
47
-
-[] (R) Minimum Two Week Window for GA e2e tests to prove flake free
48
-
-[] (R) Graduation criteria is in place
49
-
-[] (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)
50
-
-[] (R) Production readiness review completed
51
-
-[] (R) Production readiness review approved
52
-
-[] "Implementation History" section is up-to-date for milestone
53
-
-[] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
54
-
-[] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
42
+
-[x] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR)
43
+
-[x] (R) KEP approvers have approved the KEP status as `implementable`
44
+
-[x] (R) Design details are appropriately documented
45
+
-[x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
46
+
-[x] e2e Tests for all Beta API Operations (endpoints)
47
+
-[x] (R) Ensure GA e2e tests for meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md)
48
+
-[x] (R) Minimum Two Week Window for GA e2e tests to prove flake free
49
+
-[x] (R) Graduation criteria is in place
50
+
-[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)
51
+
-[x] (R) Production readiness review completed
52
+
-[x] (R) Production readiness review approved
53
+
-[x] "Implementation History" section is up-to-date for milestone
54
+
-[x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
55
+
-[x] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
@@ -280,7 +281,11 @@ So, E2E tests doesn't add extra value to integration tests.
280
281
281
282
#### Beta (v1.25):
282
283
283
-
- [ ] This feature will be enabled by default as a Beta feature in v1.25.
284
+
- [x] This feature will be enabled by default as a Beta feature in v1.25.
285
+
286
+
#### GA (v1.30):
287
+
288
+
- [x] No particular issue is reported to this feature for a certain length of time.
284
289
285
290
## Production Readiness Review Questionnaire
286
291
@@ -335,7 +340,7 @@ Scheduling of new Pods is affected.
335
340
336
341
###### Are there any tests for feature enablement/disablement?
337
342
338
-
No - unit and integration tests will be added.
343
+
No - we've only done the manual testing as described at [Were upgrade and rollback tested? Was the upgrade->downgrade->upgrade path tested?](#were-upgrade-and-rollback-tested-was-the-upgrade-downgrade-upgrade-path-tested).
339
344
340
345
### Rollout, Upgrade and Rollback Planning
341
346
@@ -424,6 +429,8 @@ logs or events for this purpose.
424
429
-->
425
430
426
431
The operator can query pods with `pod.spec.topologySpreadConstraints.minDomains` field set.
432
+
And, after adopting `minDomains` in some Pods, they can confirm that `minDomains` impacts on the scheduling
433
+
by observing an increase in `plugin_evaluation_total{plugin="PodTopologySpread",extension_point="Filter"}`.
427
434
428
435
###### How can someone using this feature know that it is working for their instance?
429
436
@@ -481,9 +488,7 @@ Describe the metrics themselves and the reasons why they weren't added (e.g., co
481
488
implementation difficulties, etc.).
482
489
-->
483
490
484
-
Yes. It would be useful if we could see which filter plugin affected Pod's scheduling results in metrics.
0 commit comments