Open anakrish opened 1 year ago
Hi @anakrish , currently we are working on optimizing image pull with stream mode(async read) support, this will also reduce the memoy consumption during image pulling but it will require some API change in oci-distribution
and ocicrypt-rs
crate.
Next we may need support on demand pull. For image layer sharing support between pods, we may need save encrypted image layers in host, then we will support on demand decrypt in guest.
For image-caching on host, were you thinking of
Here is a design proposal on how to do image caching on the host at the block level. https://docs.google.com/presentation/d/1ie4i6p17VEm5klQchjAVisMUQYFCO8rIQsT3GvGWHS4/edit#slide=id.g12878630eea_0_382
@arronwy You mention
Next we may need support on demand pull. For image layer sharing support between pods, we may need save encrypted image layers in host, then we will support on demand decrypt in guest.
Can you describe how you are planning to approach on demand pull and layer sharing?
We observed the following based on our experiments:
In a typical Kubernetes workflow, multiple pods that run on the same node would share images, improving pod startup time. This sharing is currently not possible with image-rs.
image-rs devel plan mentions: