Add OCI VolumeSource CRI API

Adding the required container runtime interface API so that runtimes and
consumers can start using it.

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
This commit is contained in:
Sascha Grunert 2024-06-24 09:46:42 +02:00
parent f24211524b
commit 448430701b
No known key found for this signature in database
GPG Key ID: 09D97D153EF94D93
2 changed files with 562 additions and 483 deletions

File diff suppressed because it is too large Load Diff

View File

@ -244,6 +244,15 @@ message Mount {
// - when set to true, readonly must be explicitly set to true, and propagation must be PRIVATE (0).
// - (readonly == false && recursive_read_only == false) does not make the mount read-only.
bool recursive_read_only = 8;
// Mount an image reference (image ID, with or without digest), which is a
// special use case for OCI volume mounts. If this field is set, then
// host_path should be unset. All OCI mounts are per feature definition
// readonly. The kubelet does an PullImage RPC and evaluates the returned
// PullImageResponse.image_ref value, which is then set to the
// ImageSpec.image field. Runtimes are expected to mount the image as
// required.
// Introduced in the OCI Volume Source KEP: https://kep.k8s.io/4639
ImageSpec image = 9;
}
// IDMapping describes host to container ID mappings for a pod sandbox.