Error map
admission webhook denied the request Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request
Kubernetes · layer 6, Platform & cloud
Centre: this error. First ring: errors it is linked with (12). 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 (12)
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.
Error: INSTALLATION FAILED: cannot re-use a name that is still in use
helm install was run with a release name that already exists in the namespace (even a failed one).
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.
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).
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.
Job has reached the specified backoff limit (BackoffLimitExceeded)
The Job’s pods failed more times than backoffLimit (default 6), so Kubernetes marked the Job failed and stopped retrying.
Kubernetes: CrashLoopBackOff
The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.
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…
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…
rendered manifests contain a resource that already exists. Unable to continue with install: ... invalid ownership metadata
Helm wants to create an object that already exists but isn’t labelled as belonging to this release.
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).
Two steps away (28)
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
ALB target unhealthy: Health checks failed with these codes: [404] / Request timed out
The load balancer’s health checks to your targets fail, so it stops sending traffic (and returns 502/503 if no targets are health…
Docker container is unhealthy (health check failing)
The container is running, but its HEALTHCHECK command keeps failing, so Docker (and dependent services) consider it unhealthy.
Error: UPGRADE FAILED: another operation (install/upgrade/rollback) is in progress
A previous Helm operation on this release was interrupted and left it in a pending-install/pending-upgrade state, so Helm refuses…
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.
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.
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.
Service has no endpoints (no endpoints available for service / Endpoints: <none>)
The Service’s selector matches no ready pods, so traffic to it is refused or returns 503.
deployment "x" exceeded its progress deadline (ProgressDeadlineExceeded)
A rollout didn’t make progress within progressDeadlineSeconds (default 600) — new pods never became ready.
The Deployment is invalid: spec.selector: Invalid value: field is immutable
You tried to change a field Kubernetes doesn’t allow to change after creation — Deployment selectors, Job templates, Service clus…
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.
Azure App Service: ":( Application Error" / container didn’t respond to HTTP pings
App Service started your app but it crashed or never listened on the expected port.
KeyError: 'x'
You accessed a dictionary key that doesn’t exist.
Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available
The scheduler can’t find a node that satisfies the pod’s resource requests, selectors, taints or volume constraints.
hint: You have divergent branches and need to specify how to reconcile them.
Git 2.27+ asks you to choose merge, rebase or fast-forward-only when local and remote both have new commits.
OCI runtime create failed: exec: "x": executable file not found in $PATH
The command you asked the container to run doesn’t exist inside the image — wrong command name, a shell that isn’t installed (bas…
Pod status InvalidImageName: couldn't parse image reference
The image field in the pod spec isn’t a valid image reference, so the kubelet can’t even try to pull it.
Pod status RunContainerError
The container was created but failed to start — usually an invalid command/entrypoint, missing interpreter, or permission problem…
Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage
The kubelet removed the pod because its node ran short of memory or disk.
Pod stuck in Terminating state
kubectl delete pod hangs and the pod shows Terminating for minutes or forever.
Failed to create pod sandbox: plugin type="calico" failed (add): ... (FailedCreatePodSandBox)
The kubelet couldn’t set up the pod’s network sandbox — almost always a CNI plugin problem or exhausted pod IPs.
Error from server (AlreadyExists): ... already exists
kubectl create tried to make an object whose name is already taken in that namespace.
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.
Map another error
Popular: 403500400TypeErrorCritical error0xC000007BNullPointerException404