CRI-O v1.35.10

CRI-O v1.35.10

The release notes have been generated for the commit range v1.35.9…8fe6c19 on Tue, 27 Oct 2026 17:20:06 UTC.

Downloads

Download one of our static release bundles via our Google Cloud Bucket:

To verify the artifact signatures via cosign, run:

> export COSIGN_EXPERIMENTAL=1
> cosign verify-blob cri-o.amd64.8fe6c1976d79b348c958a5f7658ccbf5f609a7c8.tar.gz \
    --certificate-identity https://github.com/cri-o/packaging/.github/workflows/obs.yml@refs/heads/main \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-github-workflow-repository cri-o/packaging \
    --certificate-github-workflow-ref refs/heads/main \
    --bundle cri-o.amd64.8fe6c1976d79b348c958a5f7658ccbf5f609a7c8.tar.gz.bundle

To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:

> tar xfz cri-o.amd64.8fe6c1976d79b348c958a5f7658ccbf5f609a7c8.tar.gz
> bom validate -e cri-o.amd64.8fe6c1976d79b348c958a5f7658ccbf5f609a7c8.tar.gz.spdx -d cri-o

Changelog since v1.35.9

Changes by Kind

Bug or Regression

Fix userns-mode when combined with a Kubelet supporting user namespaces. (#10442, @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. (#10343, @amritansh1502)

Uncategorized

Fixed CRI-O crash loops and stuck-Terminating pods caused by dead kata shims. (#10424, @openshift-cherrypick-robot)

Dependencies

Added

Nothing has changed.

Changed

Nothing has changed.

Removed

Nothing has changed.