Aditya Ramani 729c97cf39 Handle unexpected shim kill events ... When a shim process is unexpectedly killed in a way that was not initiated through containerd - containerd reports the pod as not ready but the containers as running. This results in kubelet repeatedly sending container kill requests that fail since containerd cannot connect to the shim. Changes: - In the container exit handler, treat `err: Unavailable` as if the container has already exited out - When attempting to get a connection to the shim, if the controller isn't available assume that the shim has been killed (needs to be done since we have a separate exit handler that cleans up the reference to the shim controller - before kubelet has the chance to call StopPodSandbox) Signed-off-by: Aditya Ramani <a_ramani@apple.com>		2023-09-18 12:15:55 -07:00
..
controller.go	Handle unexpected shim kill events	2023-09-18 12:15:55 -07:00
store.go	Add sandbox store plugin type	2022-12-20 23:05:14 -08:00