Update OCI image volume type description to remove "noexec" attribute

Signed-off-by: Ayato Tokubi <atokubi@redhat.com>

Kubernetes-commit: aa1e24659ee18378426fa3b83616c7d96e098bbe
This commit is contained in:
Ayato Tokubi
2025-12-16 16:57:37 +00:00
committed by Kubernetes Publisher
parent f66040b9dc
commit 1f85fd1a13

View File

@@ -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"`