OpenShift 4.22 introduces a Technology Preview feature that gives cluster administrators control over where CRI-O stores container image layers, OCI artifacts, and complete images. Three new ContainerRuntimeConfig API fields address key AI/ML pain points: additionalArtifactStores for placing large ML models on dedicated SSD storage, additionalImageStores for shared read-only image caches to avoid redundant registry pulls across nodes, and additionalLayerStores for lazy image pulling via plugins like stargz-store. The Machine Config Operator translates these settings into storage.conf and CRI-O drop-in config files, requiring a node reboot. All three options are gated behind the AdditionalStorageConfig feature gate under TechPreviewNoUpgrade, meaning clusters using it cannot perform minor version upgrades until GA.

7m read timeFrom developers.redhat.com
Post cover image
Table of contents
The problem: one storage location for everythingThree new storage configuration optionsHow it works under the hoodLimits and constraintsGetting startedBuilt on upstream contributionsWhat's nextLearn more

Sort: