From 9370d1ae912b35ffa44a3cb8863deccfdc23e08b Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Tue, 15 Jul 2025 10:13:16 +0200 Subject: [PATCH] Graduate image volumes to GA Signed-off-by: Sascha Grunert --- keps/sig-node/4639-oci-volume-source/README.md | 14 +++++++++----- keps/sig-node/4639-oci-volume-source/kep.yaml | 4 ++-- 2 files changed, 11 insertions(+), 7 deletions(-) diff --git a/keps/sig-node/4639-oci-volume-source/README.md b/keps/sig-node/4639-oci-volume-source/README.md index d2a23006a02..9c709eba2df 100644 --- a/keps/sig-node/4639-oci-volume-source/README.md +++ b/keps/sig-node/4639-oci-volume-source/README.md @@ -151,9 +151,9 @@ 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) - - [ ] (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] e2e Tests for all Beta API Operations (endpoints) + - [x] (R) Ensure GA e2e tests meet requirements for [Conformance Tests](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md) + - [x] (R) Minimum Two Week Window for GA e2e tests to prove flake free - [x] (R) Graduation criteria is in place - [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) - [x] (R) Production readiness review completed @@ -781,6 +781,8 @@ We expect no non-infra related flakes in the last month as a GA graduation crite - [sig-node] ImageVolume [NodeFeature:ImageVolume] should succeed with multiple pods and same image on the same node - [sig-node] ImageVolume [NodeFeature:ImageVolume] should succeed with pod and multiple volumes - [sig-node] ImageVolume [NodeFeature:ImageVolume] should succeed with pod and pull policy of Always +- [sig-node] ImageVolume [NodeFeature:ImageVolume] subPath should succeed when using a valid subPath +- [sig-node] ImageVolume [NodeFeature:ImageVolume] subPath should fail if subPath in volume is not existing https://testgrid.k8s.io/sig-node-cri-o#pr-crio-cgrpv2-imagevolume-e2e @@ -881,8 +883,6 @@ in back-to-back releases. - Multiple examples of real world uses - Production support in both CRI-O and containerd - Allowing time for feedback -- Consider a new `RuntimeConfig` field to indicate to end users if the feature - is supported or not. - Security Evaluation ensuring robust protection without the `noexec` option ### Upgrade / Downgrade Strategy @@ -1105,6 +1105,9 @@ For GA, this section is required: approvers should be able to confirm the previous answers based on experience in the field. --> +The added metrics `image_volume_requested_total` `image_volume_mounted_success` +`image_volume_mounted_error` can be used for monitoring. + ###### How can an operator determine if the feature is in use by workloads?