Kubernetes
Hard
Troubleshooting
A namespace has been stuck in Terminating for hours. What is the most likely cause?
Select your answer:
Show answer and explanation
Answer: Leftover finalizers, or an aggregated API that is unavailable
Explanation
The namespace controller deletes every object in the namespace and waits for them to disappear. An object with a finalizer stays until its controller removes the finalizer, so if that controller was uninstalled, deletion hangs. An unavailable APIService blocks it too, because the controller can't list those resources. 'kubectl get namespace <name> -o yaml' shows the reason in status.conditions.
More hard Kubernetes questions
- What does podManagementPolicy: Parallel change in a StatefulSet?
- What does volumeBindingMode: WaitForFirstConsumer on a StorageClass do?
- A slow-starting application is killed by its liveness probe before it finishes starting. What is the recommended fix?
- Which Pod Security Standards level requires pods to run as non-root, drop ALL capabilities, and use a seccomp profile?
- What is a Kubernetes Operator?
- What is a Kubernetes Admission Controller?