Cant delete pod in k8s status shows its in TerminatingState

Kubernetes
,
#1

Hello Everyone,
Failed to delete a Pod in k8s cluster.
I got this error

Warning FailedKillPod 51s kubelet error killing pod: [failed to “KillContainer” for “docker-registry-ui” with KillContainerError: “rpc error: code = Unknown desc = failed to kill container "8e15005fc7309954ec5199c8e3ae447a85a4265189505cc013b9d18bc75ece17": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”, failed to “KillContainer” for “docker-registry” with KillContainerError: “rpc error: code = Unknown desc = failed to kill container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”, failed to “KillPodSandbox” for “7e0ab945-6007-42c4-b992-ffdf54c6dc3f” with KillPodSandboxError: “rpc error: code = Unknown desc = failed to stop container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": failed to kill container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”]
Normal Killing 40s (x5 over 2m9s) kubelet Stopping container docker-registry-ui
Normal Killing 40s (x5 over 2m9s) kubelet Stopping container docker-registry
Warning FailedKillPod 10s kubelet error killing pod: [failed to “KillContainer” for “docker-registry” with KillContainerError: “rpc error: code = Unknown desc = failed to kill container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”, failed to “KillContainer” for “docker-registry-ui” with KillContainerError: “rpc error: code = Unknown desc = failed to kill container "8e15005fc7309954ec5199c8e3ae447a85a4265189505cc013b9d18bc75ece17": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”, failed to “KillPodSandbox” for “7e0ab945-6007-42c4-b992-ffdf54c6dc3f” with KillPodSandboxError: “rpc error: code = Unknown desc = failed to stop container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": failed to kill container "94232678dbd17b7d99ad4e699c1ade868bc5811ae666f7fa921284d259ad8d38": unknown error after kill: runc did not terminate successfully: exit status 1: unable to signal init: permission denied\n: unknown”]
Warning FailedMount 1s (x9 over 2m9s) kubelet MountVolume.SetUp failed for volume “kube-api-access-k55kx” : object “devops-tools”/“kube-root-ca.crt” not registered.

Need help

#2

Hi @munimdevops1111

Was this Pod consuming any volume?

This appears to be an issue with finalizers as one of the resources it uses isn’t releasing one of its sub-resources. It would help if you could check kubelet logs for any hints at journalctl -fu kubelet.

If you want to force kill it. You can edit the Pod and remove the finalizers block. That could kill the Pod.

Regards.

#3

Hello @Santosh_KodeKloud

Thank you for the reply my issue is resolved.

Issue was apparmor