Chapter 3. Bug fixes

KataConfig CR deletion removes peer pod configuration

Before this update, deleting a KataConfig custom resource (CR) with peer pods enabled did not remove the peer pod configuration. As a result, a new KataConfig CR used the old configuration and the peer pods failed to start. With this release, deleting the KataConfig CR also deletes the peer pod configuration. When the KataConfig CR is redeployed, the peer pods start up.

Optimized VM boot time on Azure

Before this update, the default disk of OpenShift sandboxed containers virtual machines (VMs) for Microsoft Azure was standard HDD. As a result, VM boot times were prolonged, causing delays in pod deployment. With this release, the default VM disk is Premium SSD, resulting in improved boot time and faster deployment.