-
Story
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
5
-
None
-
OCP Node Core Sprint 284
As a Node team engineer, I want to extend the ContainerRuntimeConfig API with additional storage configuration fields, so that cluster administrators can declaratively configure layer stores, image stores, and artifact stores for CRI-O.
Details
Extend the ContainerRuntimeConfig API in openshift/api to support advanced container storage configuration:
- additionalLayerStores - Array of layer store configurations with path field (max 5 entries)
- additionalImageStores - Array of image store configurations with path field (max 10 entries)
- additionalArtifactStores - Array of artifact store configurations with path and optional filter fields (max 10 entries)
The API extension must support path-based configuration with FUSE filesystem interface and graceful fallback.
Acceptance Criteria
- API types defined in openshift/api repository
- ContainerRuntimeConfig extended with additionalLayerStores, additionalImageStores, and additionalArtifactStores fields
- Maximum entry limits enforced (5 for layer stores, 10 for image/artifact stores)
- API validation rules implemented
- API documentation and comments added
- PR merged to openshift/api
- API changes available for MCO implementation
- depends on
-
OCPNODE-4052 Enhancement Proposal - Advanced Container Storage Configuration for CRI-O
-
- Closed
-
- is depended on by
-
OCPNODE-4074 Machine Config Operator implementation for Advanced Container Storage Configuration
-
- In Progress
-
- relates to
-
OCPNODE-4050 Additional Layer Store Support
-
- Closed
-
-
OCPNODE-4061 Additional Image Store Support
-
- Closed
-
- links to