Image Compatibility spec to ensure container and host harmony
summary
Proposal creates machine-readable image metadata so registries carry exact OS and hardware requirements, using OCI artifact records and a prototype that maps image constraints to NFD labels. It details fields like platform_compatibilities and platform features vs. weights, avoids dumping full host configs, and phases: phase one validates nodes against image metadata, phase two enforces selection via scheduler plugin or mutating webhook. OCI working group approved the effort; NFD PRs and a prototype are in progress.
AI-written summary · about
chapters (7)
- 0:00Introduction to image compatibility
- 9:30Current compatibility approaches
- 13:00OCI standardization efforts
- 18:00Artifact-based compatibility proposal
- 21:31NFD integration and phase one
- 23:38Audience Q&A session
- 31:53Future outlook and closing
related talks
30mPod fails to start? Consider OCI image compatibility
28mCNI, CRI, and OCI - Oh My! [I]
32mFive things you need to know about your container runtime
36mPanel: Native OCI Integration - Leveraging Argo CD Source Content in a Brand New Way
22mrkt and the Open Container Initiative: Promoting Industry Standards
45mNRI: Extending Containerd And CRI-O With Common Plugins
04mCRI-O: Container Runtime Intensifies
24mEnhancing CRI-O With CDI: Streamlining Device Integration in Kubernetes