The release notes have been generated for the commit range v1.29.2…c87ed38 on Thu, 11 Apr 2024 15:38:37 UTC.
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.c87ed38675bc911548fa1aad3a3a04352f2aabab.tar.gz \
--certificate-identity https://github.com/cri-o/cri-o/.github/workflows/test.yml@refs/tags/c87ed38675bc911548fa1aad3a3a04352f2aabab \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
--certificate-github-workflow-repository cri-o/cri-o \
--certificate-github-workflow-ref refs/tags/c87ed38675bc911548fa1aad3a3a04352f2aabab \
--signature cri-o.amd64.c87ed38675bc911548fa1aad3a3a04352f2aabab.tar.gz.sig \
--certificate cri-o.amd64.c87ed38675bc911548fa1aad3a3a04352f2aabab.tar.gz.cert
To verify the bill of materials (SBOM) in SPDX format using the bom tool, run:
> tar xfz cri-o.amd64.c87ed38675bc911548fa1aad3a3a04352f2aabab.tar.gz
> bom validate -e cri-o.amd64.c87ed38675bc911548fa1aad3a3a04352f2aabab.tar.gz.spdx -d cri-o
workloads config option to support CPU limits for containers that use the workloads annotations. This will expose cpuperiod and cpuquota options for a desired default value outside the norm. This feature will primarily be utilized to ensure that containers with workload annotations are correctly limited, the average use cases will not need to alter the default values. (#7959, @openshift-cherrypick-robot)Nothing has changed.
Nothing has changed.