CRI-O v1.20.3

The release notes have been generated for the commit range v1.20.2…5212621 on Wed, 14 Jul 2021 18:40:59 UTC.

Downloads

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

Fix possible segfault when image is deleted by podman while CRI-O is listing images (#4933, @haircommander)

CNI plugins are now passed a K8S_POD_UID environment variable containing the pod UID this sandbox was started for. (#5029, @dcbw)

Add the config field internal_wipe which moves the responsibility of wiping containers after a reboot and images after an upgrade from the external binary crio wipe to the main crio server. This has a handful of advantages, the main one being crio is now better able to cleanup CNI resources after a reboot. (#5014, @haircommander)
ExecSync requests now don’t use conmon, instead calling the runtime directly, which reduces overhead. (#4954, @saschagrunert)
Fix a bug where CRI-O prematurely stopped pulling from a blocked registry, even if there was a mirror for that registry it was allowed to pull from. (#5034, @haircommander)
Fix a couple of FD leaks when pulling images (#4815, @haircommander)
Fixed runtime panic if container storage layers lockfile parent directory got removed. (#5072, @saschagrunert)
Reuse connection when connecting to dbus, as well as reattempt the connection if it fails temporarily (#5058, @haircommander)

Fix a bug where an exec sync timeout would fail to cleanup the runtime exec process (#5000, @openshift-cherrypick-robot)
Fix a segfault when CRI-O has takes more than 8 minutes to create a pod or container (#4847, @openshift-cherrypick-robot)
Fix bug where cri-o would fail if tzdata package wasn’t installed (#4716, @haircommander)

Nothing has changed.