namespace Terminating Kubernetes Origin: Platform & cloud Last updated 12 Oct 2026

Namespace stuck in Terminating

A deleted namespace never disappears because some resource inside it, or the namespace’s own finalizer, can’t be cleaned up.

Exact message you may see namespace stuck in TerminatingSome content in the namespace has finalizers remaining
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

Namespace deletion waits until every object inside is gone. Unavailable aggregated APIs (metrics.k8s.io, a removed webhook/CRD controller) or custom resources with finalizers block it. kubectl describe ns shows NamespaceContentRemaining / NamespaceFinalizersRemaining conditions.

Common causes

  • CRD instances with finalizers whose controller was uninstalled
  • Unavailable APIService (e.g. v1beta1.metrics.k8s.io)
  • Stuck PVCs/pods inside

⚡ Quick fix

  1. kubectl describe ns to see what remains
  2. Fix or delete broken APIServices
  3. Remove finalizers from leftover resources (only if their controller is gone)

Detailed fix by platform

Kubernetes

  1. bash
    kubectl describe ns old-app | sed -n '/Conditions/,$p'
kubectl get apiservice | grep False
kubectl api-resources --verbs=list --namespaced -o name | xargs -n1 kubectl get -n old-app --ignore-not-found --show-kind

How to diagnose

  1. Conditions — What content/finalizers remain?
  2. APIs — Unavailable APIServices?
  3. CRDs — Controllers still installed?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

admission webhook denied the request — Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request (Kubernetes)admission webhook den…CrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOfffailed calling webhook — Internal error occurred: failed calling webhook "x": ... connection refused / context deadline exceeded (Kubernetes)failed calling webhookis waiting to start — Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating (Kubernetes)is waiting to startMetrics API not available — error: Metrics API not available / HPA: unable to get metrics for resource cpu (Kubernetes)Metrics API not avail…No resources found — No resources found in default namespace (Kubernetes)No resources foundNotFound — Error from server (NotFound): deployments.apps "x" not found (Kubernetes)NotFoundTerminating — Pod stuck in Terminating state (Kubernetes)Terminatingnamespace…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.