I have an on-prem kubeadm created Kubernetes cluster running on Ubuntu 18.04. I have installed cri-o as container runtime. Since, it is claimed by CRI-O that it supports zero downtime during live upgrades, as it doesn't restart the containers when the CRI-O service is restarted.
In my cluster, when I restart cri-o service (systemctl restart crio), all the containers are restarted. Is there any specific configuration that I am missing that will avoid the restart of the container when the cri-o daemon is restarted?