Enhancing CRI-O With CDI: Streamlining Device Integration in Kubernetes

on YouTube ↗24m

" summary

CRI-O reads CDI spec files to convert vendor device descriptions into concrete container changes: it reads /etc/cdi and /run/cdi, locates fully qualified device names passed by kubelet, and modifies OCI runtime spec (mounts, /dev nodes, env and OCI hooks) on the fly without restart. Device plugins or DRA return CDI names; a demo uses four A100 GPUs and shows resource claims creating and removing CDI specs dynamically. Defaults are configurable and vendors (e.g., Nvidia) generate the CDI files and hooks that make complex devices usable inside containers.

AI-written summary · about

" chapters (7)

1. 0:00CRI-O and CDI intro
2. 1:53CRI-O as Kubernetes runtime
3. 3:19CDI fundamentals
4. 6:55CDI with CRI-O for devices
5. 10:47CDI benefits in CRI-O
6. 13:36Live demo: NVIDIA GPUs in CRI-O
7. 17:56Q&A: GPU fractions

" related talks

• 45mNRI: Extending Containerd And CRI-O With Common PluginsKrisztian Litkey, Mike Brown · KubeCon + CloudNativeCon North America 2022
• 38mIntroduction to CRI-OMrunal Patel, Peter Hunt · KubeCon + CloudNativeCon North America 2019
• 31mCRI-O: The Runtime Control RoomSascha Grunert, Mrunal Patel, Peter Hunt, Urvashi Mohnani · KubeCon + CloudNativeCon North America 2020 Virtual
• 33mCRI-O Still Loves KubernetesMrunal Patel, Peter Hunt, Urvashi Mohnani, Sasha Grunert · KubeCon + CloudNativeCon Europe 2021
• 29mCRI-O: All the Runtime Kubernetes Needs, and Nothing MoreMrunal Patel · KubeCon + CloudNativeCon North America 2017
• 37mCRI-O: Under the HoodSascha Grunert, Mrunal Patel · KubeCon + CloudNativeCon North America 2019
• 46mCRI-O: All the Runtime Kubernetes needAntonio Mudarca · QCon São Paulo 2018
• 28mCNI, CRI, and OCI - Oh My! [I]Paul Burt, Elsie Phillips · KubeCon + CloudNativeCon North America 2017