Kubernetes Image Volumes, introduced as alpha in v1.31, graduates to beta in v1.33. The feature remains disabled by default due to limited container runtime support. CRI-O v1.31 offers initial support, with beta support coming in v1.33, while containerd's alpha support arrives in v2.1.0, with beta in progress. Key beta enhancements include subPath and subPathExpr support for mounting specific image subdirectories read-only. Non-existent subdirectories cannot be mounted, and Kubernetes validates paths for safety. Runtimes must also verify paths, reporting errors via kubelet events. Three new kubelet metrics track image volume requests, successful mounts, and mount errors. Users can specify subPath or subPathExpr within volumeMounts to mount existing subdirectories. An example demonstrates mounting a subdirectory named dir within a pod. This blog post celebrates the feature's beta graduation, acknowledging contributors and encouraging feedback through Slack or the SIG Node mailing list. Further reading resources on using image volumes with pods and an image volume overview are available.
subPathandsubPathExprsupport for mounting specific image subdirectories read-only. Non-existent subdirectories cannot be mounted, and Kubernetes validates paths for safety. Runtimes must also verify paths, reporting errors via kubelet events. Three new kubelet metrics track image volume requests, successful mounts, and mount errors. Users can specifysubPathorsubPathExprwithinvolumeMountsto mount existing subdirectories. An example demonstrates mounting a subdirectory nameddirwithin a pod. This blog post celebrates the feature's beta graduation, acknowledging contributors and encouraging feedback through Slack or the SIG Node mailing list. Further reading resources on using image volumes with pods and an image volume overview are available.