RATATOSKRATATOSK
Sign in

CRI-O

v1.36.8Kubernetes Core
Nov 3, 2026

CHECK 1OTHER 6

A maintenance release focused on correctness fixes also changes the release bundle SBOM format. Validation tooling may need updating because `bom` v0.8.0 or later is required.

Check if affected (1)

  • breakingThe bom version requirement for SBOM validation

    Applies if you use bom.

    Validating release bundle SBOMs with bom requires v0.8.0 or later.

All 6 other recorded changesfixes 5 · value changes 1

fixes (5)

  • - Fixed exclusive CPU cleanup when cgroups disappear during container cleanup. (#10469, @bitoku)
  • - Fix userns-mode when combined with a Kubelet supporting user namespaces. (#10433, @openshift-cherrypick-robot)
  • - When crio.service is restarted while containers are being created, an in-flight conmon process can still be killed and its crio-conmon-*.scope unit can still enter a failed state. That scope is now automatically garbage collected by systemd instead of persisting in systemctl --failed indefinitely. (#10476, @openshift-cherrypick-robot)
  • - Fix SELinux labeling so systemd/init containers receive container_init_t again instead of remaining container_t and failing to create cgroups. (#10457, @aksjadha)
  • - Fixed CRI-O crash loops and stuck-Terminating pods caused by dead kata shims. (#10423, @openshift-cherrypick-robot)

value changes (1)

  • - The release bundle SBOMs are now SPDX 3.0.1 JSON-LD files suffixed with .spdx.json instead of SPDX 2.3 tag-value .spdx files. Validating them with bom requires v0.8.0 or later. (#10396, @saschagrunert)
Add CRI-O to your stack

A weekly email arrives when a release needs action. Like the breaking changes in this release.

Add to stack →
Official release note ↗All CRI-O releases →