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
Copy file name to clipboardExpand all lines: keps/sig-scheduling/3094-pod-topology-spread-considering-taints/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,8 +138,8 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
138
138
-[ ] (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)
139
139
-[ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
140
140
-[x] (R) Graduation criteria is in place
141
-
-[] (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)
142
-
-[] (R) Production readiness review completed
141
+
-[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)
142
+
-[x] (R) Production readiness review completed
143
143
-[ ] (R) Production readiness review approved
144
144
-[x] "Implementation History" section is up-to-date for milestone
145
145
-[x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
@@ -566,7 +566,7 @@ feature, can it break the existing applications?).
566
566
567
567
NOTE: Also set `disable-supported` to `true` or `false` in `kep.yaml`.
568
568
-->
569
-
Yes, we can just disable the feature gate.
569
+
No, but once you leave the related fields unset, this feature will not work.
570
570
571
571
###### What happens if we reenable the feature if it was previously rolled back?
0 commit comments