diff --git a/keps/prod-readiness/sig-node/4009.yaml b/keps/prod-readiness/sig-node/4009.yaml index dab70122035..83c6bacc739 100644 --- a/keps/prod-readiness/sig-node/4009.yaml +++ b/keps/prod-readiness/sig-node/4009.yaml @@ -3,3 +3,5 @@ alpha: approver: "@johnbelamaric" beta: approver: "@johnbelamaric" +stable: + approver: "@johnbelamaric" diff --git a/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/README.md b/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/README.md index 072f2648f8b..106fbea4b1c 100644 --- a/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/README.md +++ b/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/README.md @@ -34,19 +34,19 @@ Items marked with (R) are required *prior to targeting to a milestone / release*. -- [ ] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR) -- [ ] (R) KEP approvers have approved the KEP status as `implementable` -- [ ] (R) Design details are appropriately documented +- [X] (R) Enhancement issue in release milestone, which links to KEP dir in [kubernetes/enhancements] (not the initial KEP PR) +- [X] (R) KEP approvers have approved the KEP status as `implementable` +- [X] (R) Design details are appropriately documented - [ ] (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 -- [ ] (R) Graduation criteria is in place +- [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) -- [ ] (R) Production readiness review completed -- [ ] (R) Production readiness review approved -- [ ] "Implementation History" section is up-to-date for milestone -- [ ] User-facing documentation has been created in [kubernetes/website], for publication to [kubernetes.io] +- [x] (R) Production readiness review completed +- [x] (R) Production readiness review approved +- [X] "Implementation History" section is up-to-date for milestone +- [X] 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 [kubernetes.io]: https://kubernetes.io/ @@ -153,14 +153,14 @@ However, these cases will be added in the existing integration tests: ##### e2e tests -These cases will be added in the existing `e2e_node` tests: - - Device Plugin works with CDI devices +This test case has been added to the existing `e2e_node` tests: + - DevicePlugin can make a CDI device accessible in a container -Links to tests: -- TBD: Will fill-in by code freeze +Links to test grid: +- https://testgrid.k8s.io/sig-node-containerd#e2e-cos-device-plugin-gpu Links to k8s-triage for tests: -- TBD: Will fill-in by code freeze +- https://storage.googleapis.com/k8s-triage/index.html?test=DevicePlugin ### Graduation Criteria @@ -351,6 +351,7 @@ N/A - 2023-05-15: KEP created - 2023-09-25: KEP updated to mark transition to beta +- 2024-01-24: KEP updated to mark transition to stable ## Drawbacks diff --git a/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/kep.yaml b/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/kep.yaml index 34d251c0184..b3d1e8945ea 100644 --- a/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/kep.yaml +++ b/keps/sig-node/4009-add-cdi-devices-to-device-plugin-api/kep.yaml @@ -18,12 +18,12 @@ see-also: replaces: [] # The target maturity stage in the current dev cycle for this KEP. -stage: beta +stage: stable # 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.29" +latest-milestone: "v1.30" # The milestone at which this feature was, or is targeted to be, at each stage. milestone: