CRI-O v1.35.2

CRI-O v1.35.2

The release notes have been generated for the commit range v1.35.1…b7a5104 on Thu, 30 Apr 2026 14:18:23 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.b7a5104af3476a12cbe64ecaa7879511317a3083.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.b7a5104af3476a12cbe64ecaa7879511317a3083.tar.gz.bundle

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

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

Changelog since v1.35.1

Changes by Kind

Feature

CRI-O now continuously monitors CNI plugin health using the STATUS verb. If a plugin becomes unhealthy after initial readiness, the node is reported as NetworkReady=false, preventing pod scheduling on affected nodes. The node self-heals when the plugin recovers. (#9903, @haircommander)

Bug or Regression

PullImage now returns the image ID directly, ensuring compatibility with Kubernetes credential verification for image pulls. (#9826, @haircommander)

Uncategorized

Add container_runtime_crio_default_runtime metric to display which default runtime the node is configured to use (#9897, @openshift-cherrypick-robot)
Add min_injected_gomaxprocs option, which allows a user to specify GOMAXPROCS in every container CRI-O creates. The config field itself is an integer that represents the floor of GOMAXPROCS. CRI-O will inject max(floor, cpu.request), if the pod is not a guaranteed pod or is part of a partitioned workload (#9876, @openshift-cherrypick-robot)
Added support for configuring additional read-only artifact stores via the additional_artifact_stores configuration option. (#9829, @openshift-cherrypick-robot)
Fix CVE-2026-35469 by updating spdystream dependency (#9883, @openshift-cherrypick-robot)
Fixed a bug where CRI-O didn’t return all metrics when “all” is set. (#9781, @openshift-cherrypick-robot)
Fixed a panic when concurrent StopContainer calls race against the stop lifecycle completing. (#9814, @openshift-cherrypick-robot)
Fixed cases where regular container images could accidentally be pulled into the OCI artifact store (#9788, @openshift-cherrypick-robot)
Fixed the race condition where cri-o reports exitCode 255 when the container exits fast. (#9871, @openshift-cherrypick-robot)
Respect the same pinned_images configuration used by regular container images (#9838, @openshift-cherrypick-robot)
Revert CRI-O CNI monitoring, as it has caused node bootstrapping regressions (#9908, @haircommander)

Dependencies

Added

Nothing has changed.

Changed

github.com/moby/spdystream: v0.5.0 → v0.5.1

Removed

Nothing has changed.