OCI Hooks: Enhancing Kubernetes Runtime Management
summary
Built a wasp-agent that enables pod swap by installing a postStart hook into CRI-O’s rendered OCI config so virtual machine pods consume swap; it works but exposes three problems: hooks run statelessly as forked executables, race with runtime cgroup settings, and are hard to debug. The talk maps CRI, OCI, kubelet, CRI-O and runc to that implementation, shows cgroup and debugging use cases, and recommends Node Resource Interface (NRI) as a stateful, gRPC-backed alternative to hook into CRI calls.
AI-written summary · about
chapters (9)
- 0:00OCI hooks intro
- 1:05Container history modularity
- 3:18Runtime specs engines
- 7:57Kubernetes integration
- 10:48OCI hooks use cases
- 13:36Configuring OCI hooks
- 17:30Debugging OCI hooks
- 19:39NRI alternative
- 21:11Summary tips
