From 1f85fd1a130288ca06585c111ede15ca3acaf6ef Mon Sep 17 00:00:00 2001 From: Ayato Tokubi Date: Tue, 16 Dec 2025 16:57:37 +0000 Subject: [PATCH] Update OCI image volume type description to remove "noexec" attribute Signed-off-by: Ayato Tokubi Kubernetes-commit: aa1e24659ee18378426fa3b83616c7d96e098bbe --- applyconfigurations/core/v1/volumesource.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/applyconfigurations/core/v1/volumesource.go b/applyconfigurations/core/v1/volumesource.go index 4f8e2c07d..2ce585f54 100644 --- a/applyconfigurations/core/v1/volumesource.go +++ b/applyconfigurations/core/v1/volumesource.go @@ -162,7 +162,7 @@ type VolumeSourceApplyConfiguration struct { // A failure to resolve or pull the image during pod startup will block containers from starting and may add significant latency. Failures will be retried using normal volume backoff and will be reported on the pod reason and message. // The types of objects that may be mounted by this volume are defined by the container runtime implementation on a host machine and at minimum must include all valid types supported by the container image field. // The OCI object gets mounted in a single directory (spec.containers[*].volumeMounts.mountPath) by merging the manifest layers in the same way as for container images. - // The volume will be mounted read-only (ro) and non-executable files (noexec). + // The volume will be mounted read-only (ro). // Sub path mounts for containers are not supported (spec.containers[*].volumeMounts.subpath) before 1.33. // The field spec.securityContext.fsGroupChangePolicy has no effect on this volume type. Image *ImageVolumeSourceApplyConfiguration `json:"image,omitempty"`