Error map
namespace Terminating Namespace stuck in Terminating
Kubernetes · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (8). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.
Directly related (8)
error: Metrics API not available / HPA: unable to get metrics for resource cpu
metrics-server isn’t installed or isn’t working, so kubectl top and CPU/memory HorizontalPodAutoscalers have no data.
Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request
A validating admission webhook (ingress-nginx, Gatekeeper/OPA, Kyverno) inspected your object and rejected it; the reason follows…
Internal error occurred: failed calling webhook "x": ... connection refused / context deadline exceeded
The API server couldn’t reach an admission webhook’s service, so it rejected the request (failurePolicy: Fail).
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
Error from server (BadRequest): container "x" in pod "y" is waiting to start: ContainerCreating
kubectl logs has nothing to show yet — the container hasn’t started (still creating, pulling, or blocked).
No resources found in default namespace
Not an error: kubectl found nothing of that kind in the namespace it looked in — usually because the resources are in another nam…
Error from server (NotFound): deployments.apps "x" not found
The named object doesn’t exist in the namespace/cluster kubectl is pointing at.
Pod stuck in Terminating state
kubectl delete pod hangs and the pod shows Terminating for minutes or forever.
Two steps away (23)
Kubernetes: CreateContainerConfigError — secret / configmap not found
Kubernetes can’t build the container’s configuration — usually a referenced Secret, ConfigMap or key doesn’t exist in that namesp…
Pod status CreateContainerError
The image was pulled, but the container runtime failed to create the container — bad command, missing mount target, or a name/vol…
pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory
A ResourceQuota on the namespace covers CPU/memory, so every pod must declare those requests/limits — and this one doesn’t.
Readiness probe failed: HTTP probe failed with statuscode: 503 / connect: connection refused
The container is running, but its readiness check fails, so the pod is marked not ready and removed from Service endpoints.
Liveness probe failed ... Container will be restarted (also Startup probe failed)
The kubelet’s liveness (or startup) check failed enough times that it killed and restarted the container.
Kubernetes node NotReady (Kubelet stopped posting node status)
The control plane hasn’t heard from a node’s kubelet, or the kubelet reports a problem — pods there stop being scheduled and are…
Webhook signature verification failed (Stripe, Razorpay, GitHub…)
Your endpoint computed a different HMAC signature than the one the provider sent, so the webhook is rejected.
Webhook delivery failed (endpoint returned non-2xx / timed out)
The provider tried to send a webhook to your endpoint but didn’t get a timely 2xx response, so it marks the delivery failed and r…
Error creating: pods is forbidden: violates PodSecurity "restricted:latest": allowPrivilegeEscalation != false ...
The namespace enforces a Pod Security Standard (baseline/restricted) and the pod spec breaks one of its rules.
no space left on device (Docker / Linux)
The disk (or inode table) is full — Docker images, build cache, logs and volumes are common culprits.
Kubernetes: ImagePullBackOff / ErrImagePull
The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
HTTP 500 Internal Server Error
The server hit an unexpected condition — usually an unhandled exception or misconfiguration in the application.
HTTP 499 Client Closed Request (Nginx)
Nginx-specific code logged when the client disconnected before the server finished responding.
kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port?
kubectl has no usable kubeconfig, so it falls back to localhost:8080 — or the cluster API server is unreachable.
Error from server (Forbidden): pods is forbidden: User "x" cannot list resource "pods" in API group "" in the namespace
You’re authenticated to the cluster, but RBAC doesn’t give your user or service account that verb on that resource.
Unable to connect to the server: x509: certificate has expired or is not yet valid / certificate signed by unknown authority
kubectl doesn’t trust the API server’s certificate — it expired (kubeadm clusters after 1 year), the CA in kubeconfig is wrong, o…
Error from server (AlreadyExists): ... already exists
kubectl create tried to make an object whose name is already taken in that namespace.
error: You must be logged in to the server (Unauthorized)
The cluster rejected kubectl’s credentials — expired token, wrong kubeconfig user, or cloud IAM identity not allowed.
Unable to connect to the server: dial tcp <ip>:443: i/o timeout
kubectl can’t reach the API server at all — network path, VPN, firewall or a private endpoint you’re outside of.
error: the server doesn't have a resource type "x"
kubectl doesn’t know the resource name you typed — a typo, a CRD that isn’t installed, or a stale discovery cache.
Pod stuck ContainerCreating: MountVolume.SetUp failed / Unable to attach or mount volumes: timed out waiting for the condition
The kubelet couldn’t mount one of the pod’s volumes, so the pod stays in ContainerCreating.
Pod status Init:CrashLoopBackOff / Init:Error
An init container keeps failing, so the pod’s main containers never start.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException