Comment 2 for bug 1853653

I did a test deployment where I started with containerd 1.2.6 and upgraded to 1.3.0. It looks like the impact is pretty small. The only impact I observed was that I got kicked out of a `kubectl exec` session, but I was able to restart it immediately after. Pod containers were not restarted. Integration tests showed no issues following the upgrade.

The containerd apt package maintainer indicated that there should be no major issues with updating the package to 1.3.0, and we can request it by opening an issue here: https://bugs.launchpad.net/ubuntu/+source/containerd

I'm going to sync with the team before moving forward. Expect an update on this issue sometime next week.