What is the problem you're trying to solve

Looks like containerd runtime doesn't support a SIGRTMIN+3 stopsignal ?

Seeing the error below in an AKS cluster after upgrade to AKS 1.19.x (which switch from docker/moby to containerd runtime):

E0421 12:00:00.000 4252 pod_workers.go:191] Error syncing pod XYZ ("mypod(XYZ)"), skipping: failed to "KillContainer" for "ABC" with KillContainerError: "rpc error: code = Unknown desc = failed to parse stop signal "SIGRTMIN+3": **unknown signal "SIGRTMIN+3""**

Describe the solution you'd like

I'd like containerd to handle this type of stopsignal, just like docker does.