Runbook

Troubleshooting Non-Terminating Kubernetes Pods.

Back to Runbooks

Overview

This incident type refers to the problem of Kubernetes pods that are not terminating. When a pod is no longer needed, it should terminate automatically. However, sometimes a pod can get stuck in a state where it is not terminating, even though it is no longer needed. This can be caused by a variety of factors, such as network issues, resource constraints, or bugs in the application code. Troubleshooting non-terminating Kubernetes pods involves identifying the root cause of the issue and taking steps to resolve it, such as restarting the pod, freeing up resources, or fixing bugs in the code.

Parameters

Debug

Get detailed information about a specific pod

Check the logs of a specific container within a pod

See what is still running on the specific pod

Check the status of the Kubernetes components

Check the Kubernetes API server logs

Check the Kubernetes controller manager logs

Check the Kubernetes scheduler logs

Show any finalizers associated with the pod.

Repair

Forcefully delete a stuck pod (WARNING: this may cause data loss)

Remove any finalizers associated with the pod.

Learn more

Related Runbooks

Check out these related runbooks to help you debug and resolve similar issues.