DRA device taints: document state in 1.35 and plan beta in 1.36

Author: pohly

keps/prod-readiness/sig-scheduling/5055.yaml

@@ -4,3 +4,5 @@
 kep-number: 5055
 alpha:
   approver: "@soltysh"
+beta:
+  approver: "@soltysh"

keps/sig-scheduling/5055-dra-device-taints-and-tolerations/README.md

@@ -122,16 +122,16 @@ Items marked with (R) are required *prior to targeting to a milestone / release*
 - [x] (R) KEP approvers have approved the KEP status as `implementable`
 - [x] (R) Design details are appropriately documented
 - [x] (R) Test plan is in place, giving consideration to SIG Architecture and SIG Testing input (including test refactors)
-  - [ ] e2e Tests for all Beta API Operations (endpoints)
+  - [x] e2e Tests for all Beta API Operations (endpoints)
   - [ ] (R) Ensure GA e2e tests meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md) 
   - [ ] (R) Minimum Two Week Window for GA e2e tests to prove flake free
 - [x] (R) Graduation criteria is in place
   - [ ] (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) 
 - [x] (R) Production readiness review completed
 - [x] (R) Production readiness review approved
 - [x] "Implementation History" section is up-to-date for milestone
-- [ ] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
-- [ ] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
+- [x] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io]
+- [x] Supporting documentation—e.g., additional design documents, links to mailing list discussions/SIG meetings, relevant PRs/issues, release notes
 
 <!--
 **Note:** This checklist is iterative and should be reviewed and updated every time this enhancement is being considered for a milestone.
@@ -174,8 +174,7 @@ ResourceClaim.
 
 ### Non-Goals
 
-- Not part of the plan for alpha: developing a kubectl command for managing device taints.
-  This may be reconsidered.
+- Not part of the plan for this KEP: developing a kubectl command for managing device taints.
 
 ## Proposal
 
@@ -240,8 +239,7 @@ Without a kubectl extension similar to `kubectl taint nodes`, the user
 experience for admins will be a bit challenging. They need to decide how to
 identify the device (by name or with a CEL expression), manually create a
 DeviceTaintRule with a unique name, then remember to remove that
-DeviceTaintRule again. For beta, support in `kubectl` for common
-operations may be needed.
+DeviceTaintRule again.
 
 Users might be tempted to tolerate taints to get their pods running. They do
 that at their own risk. Depending on the taint, the application then may not

keps/sig-scheduling/5055-dra-device-taints-and-tolerations/kep.yaml

@@ -21,11 +21,13 @@ stage: alpha
 # The most recent milestone for which work toward delivery of this KEP has been
 # done. This can be the current (upcoming) milestone, if it is being actively
 # worked on.
-latest-milestone: "v1.35"
+latest-milestone: "v1.36"
 
 # The milestone at which this feature was, or is targeted to be, at each stage.
 milestone:
   alpha: "v1.33"
+  beta: "v1.36"
+  stable: "v1.37"
 
 # The following PRR answers are required at alpha release
 # List the feature gate name and the components for which it must be enabled
@@ -35,6 +37,11 @@ feature-gates:
       - kube-apiserver
       - kube-scheduler
       - kube-controller-manager
+  - name: DRADeviceTaintRules
+    components:
+      - kube-apiserver
+      - kube-scheduler
+      - kube-controller-manager
 disable-supported: true
 
 # The following PRR answers are required at beta release