CRI-O v1.30.0

The release notes have been generated for the commit range v1.29.0…3923f4f on Fri, 03 May 2024 05:41:52 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.3923f4f1745819983c0f9f952d05d1f67eec8979.tar.gz \
    --certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/3923f4f1745819983c0f9f952d05d1f67eec8979 \
    --certificate-oidc-issuer https://token.actions.githubusercontent.com \
    --certificate-github-workflow-repository cri-o/cri-o \
    --certificate-github-workflow-ref refs/tags/3923f4f1745819983c0f9f952d05d1f67eec8979 \
    --signature cri-o.amd64.3923f4f1745819983c0f9f952d05d1f67eec8979.tar.gz.sig \
    --certificate cri-o.amd64.3923f4f1745819983c0f9f952d05d1f67eec8979.tar.gz.cert

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

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

Changelog since v1.29.0

Changes by Kind

Other

Dependency-Change

Ci

Deprecation

The AppArmor profile to the CRI via the deprecated apparmor_profile field in favor of the newer structured apparmor field. CRI provides the AppArmor profile via both fields to maintain backwards compatibility. ref https://github.com/kubernetes/kubernetes/pull/123811 Process new field and fallback to deprecated. From the kubernetes side both fields are populated. (#7901, @roman-kiselenko)

API Change

Feature

Bug or Regression

Other (Cleanup or Flake)

Uncategorized

Dependencies

Added

Changed

Removed