Error map

PDB GKE node upgrade stuck: PodDisruptionBudget blocks the drain

Google Cloud / Firebase · layer 6, Platform & cloud

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). 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.

PDB — GKE node upgrade stuck: PodDisruptionBudget blocks the drain (Google Cloud / Firebase)PDBFailedScheduling — Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available (Kubernetes)FailedSchedulingGKE: Quota 'CPUS' exceeded — GKE/Compute: Quota 'CPUS' exceeded. Limit: 8.0 in region us-central1 (QUOTA_EXCEEDED) (Google Cloud / Firebase)GKE: Quota 'CPUS' e…GKE: 0/3 nodes are available: Insufficient cpu — GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu (Google Cloud / Firebase)GKE: 0/3 nodes are …gke-gcloud-auth-plugin not found — kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed (Google Cloud / Firebase)gke-gcloud-auth-plu…GKE Ingress: backends marked UNHEALTHY (502) — GKE Ingress: Some backend services are in UNHEALTHY state / 502 Server Error from the load balancer (Google Cloud / Firebase)GKE Ingress: backen…Autopilot — GKE Autopilot rejected the workload: resources adjusted / violates Autopilot constraints (Google Cloud / Firebase)AutopilotImagePullBackOff — GKE ImagePullBackOff: 403 Forbidden pulling from Artifact Registry (node service account lacks reader) (Google Cloud / Firebase)ImagePullBackOffCrashLoopBackOff — Kubernetes: CrashLoopBackOff (Kubernetes)CrashLoopBackOffImagePullBackOff — Kubernetes: ImagePullBackOff / ErrImagePull (Kubernetes)ImagePullBackOffCreateContainerConfigError — Kubernetes: CreateContainerConfigError — secret / configmap not found (Kubernetes)CreateContainerConf…Workload Identity 403: Permission denied (GKE) — GKE: google.api_core.exceptions.Forbidden: 403 Caller does not have required permission — Workload Identity: unable to generate access token (Google Cloud / Firebase)Workload Identity 4…429 RESOURCE_EXHAUSTED: Quota exceeded for quota metric — Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user' (Google Cloud / Firebase)429 RESOURCE_EXHAUS…ZONE_RESOURCE_POOL_EXHAUSTED — Compute Engine: The zone 'projects/p/zones/us-central1-a' does not have enough resources available to fulfill the request (ZONE_RESOURCE_POOL_EXHAUSTED) (Google Cloud / Firebase)ZONE_RESOURCE_POOL_…OOMKilled — Kubernetes: OOMKilled (exit code 137) (Kubernetes)OOMKilledAPI has not been used in project before or it is disabled — Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting (Google Cloud / Firebase)API has not been us…Your active project does not match the quota project in your local ADC — gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file (Google Cloud / Firebase)Your active project…kubectl connection refused — kubectl: The connection to the server localhost:8080 was refused — did you specify the right host or port? (Kubernetes)kubectl connection …Forbidden — Error from server (Forbidden): pods is forbidden: User "x" cannot list resource "pods" in API group "" in the namespace (Kubernetes)ForbiddenYou must be logged in to the server — error: You must be logged in to the server (Unauthorized) (Kubernetes)You must be logged …Readiness probe failed — Readiness probe failed: HTTP probe failed with statuscode: 503 / connect: connection refused (Kubernetes)Readiness probe fai…default backend - 404 — Ingress returns "404 Not Found" / "default backend - 404" (ingress-nginx) (Kubernetes)default backend - 4…admission webhook denied the request — Error from server: admission webhook "validate.nginx.ingress.kubernetes.io" denied the request (Kubernetes)admission webhook d…E11000 duplicate key — MongoServerError: E11000 duplicate key error collection: db.users index: email_1 dup key (Node.js)E11000 duplicate keyPrisma P2002 — PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`) (Node.js)Prisma P2002SQLAlchemy IntegrityError — sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint (Python)SQLAlchemy Integrit…Cloud Run 403: Your client does not have permission to get URL — Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server (Google Cloud / Firebase)Cloud Run 403: Your…Cloud Run: Image not found / failed to pull — Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied (Google Cloud / Firebase)Cloud Run: Image no…BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permission — BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project (Google Cloud / Firebase)BigQuery: Access De…

Directly related (7)

FailedSchedulingKubernetes

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.

GKE: Quota 'CPUS' exceededGoogle Cloud / Firebase

GKE/Compute: Quota 'CPUS' exceeded. Limit: 8.0 in region us-central1 (QUOTA_EXCEEDED)

Creating nodes or clusters needs more vCPUs than your project's regional quota allows.

GKE: 0/3 nodes are available: Insufficient cpuGoogle Cloud / Firebase

GKE/Kubernetes: Pod unschedulable — 0/3 nodes are available: 3 Insufficient cpu

The scheduler found no node with enough free CPU/memory for the pod's resource requests.

gke-gcloud-auth-plugin not foundGoogle Cloud / Firebase

kubectl: error: executable gke-gcloud-auth-plugin not found — it looks like you are trying to use a client-go credential plugin that is not installed

kubectl needs the `gke-gcloud-auth-plugin` binary to authenticate to GKE, and it is missing from PATH.

GKE Ingress: backends marked UNHEALTHY (502)Google Cloud / Firebase

GKE Ingress: Some backend services are in UNHEALTHY state / 502 Server Error from the load balancer

The Google load balancer's health checks fail for the Ingress backends, so it returns 502 or 'no healthy upstream'.

AutopilotGoogle Cloud / Firebase

GKE Autopilot rejected the workload: resources adjusted / violates Autopilot constraints

Autopilot modifies or rejects pods that don't meet its rules (requests/limits, privileged settings, host access).

ImagePullBackOffGoogle Cloud / Firebase

GKE ImagePullBackOff: 403 Forbidden pulling from Artifact Registry (node service account lacks reader)

Nodes can't pull your image because their service account has no read access to the registry.

Two steps away (21)

CrashLoopBackOffKubernetes

Kubernetes: CrashLoopBackOff

The container starts, crashes (or exits), and Kubernetes keeps restarting it with increasing back-off delays.

ImagePullBackOffKubernetes

Kubernetes: ImagePullBackOff / ErrImagePull

The node can’t pull the container image — wrong name/tag, missing registry credentials, or registry unreachable.

CreateContainerConfigErrorKubernetes

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…

Workload Identity 403: Permission denied (GKE)Google Cloud / Firebase

GKE: google.api_core.exceptions.Forbidden: 403 Caller does not have required permission — Workload Identity: unable to generate access token

A pod tried to call Google APIs but its Kubernetes service account is not bound to a Google service account (or the binding lacks…

429 RESOURCE_EXHAUSTED: Quota exceeded for quota metricGoogle Cloud / Firebase

Google API: 429 RESOURCE_EXHAUSTED — Quota exceeded for quota metric 'Read requests' and limit 'Read requests per minute per user'

Your project or user exceeded an API rate or daily quota.

ZONE_RESOURCE_POOL_EXHAUSTEDGoogle Cloud / Firebase

Compute Engine: The zone 'projects/p/zones/us-central1-a' does not have enough resources available to fulfill the request (ZONE_RESOURCE_POOL_EXHAUSTED)

Google has no spare capacity for that machine type in the zone right now.

OOMKilledKubernetes

Kubernetes: OOMKilled (exit code 137)

The container used more memory than its limit, and the kernel killed it.

API has not been used in project before or it is disabledGoogle Cloud / Firebase

Google Cloud: 403 SERVICE_DISABLED — Cloud Resource Manager API has not been used in project 123456 before or it is disabled. Enable it by visiting

The Google API you called is not enabled for the project that the request is billed to.

Your active project does not match the quota project in your local ADCGoogle Cloud / Firebase

gcloud/ADC: WARNING: Your active project does not match the quota project in your local Application Default Credentials file

Application Default Credentials bill API usage to a different project than the one you have set as active, which can cause surpri…

kubectl connection refusedKubernetes

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.

ForbiddenKubernetes

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.

You must be logged in to the serverKubernetes

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.

Readiness probe failedKubernetes

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.

default backend - 404Kubernetes

Ingress returns "404 Not Found" / "default backend - 404" (ingress-nginx)

The ingress controller received the request but no Ingress rule matched the host/path, so it answered with its default backend.

admission webhook denied the requestKubernetes

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…

E11000 duplicate keyNode.js

MongoServerError: E11000 duplicate key error collection: db.users index: email_1 dup key

An insert/update violated a unique index in MongoDB.

Prisma P2002Node.js

PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)

A Prisma create/update violated a unique constraint.

SQLAlchemy IntegrityErrorPython

sqlalchemy.exc.IntegrityError: (psycopg2.errors.UniqueViolation) duplicate key value violates unique constraint

A database constraint (unique, foreign key, not null) rejected an insert/update made through SQLAlchemy.

Cloud Run 403: Your client does not have permission to get URLGoogle Cloud / Firebase

Cloud Run: Error: Forbidden — Your client does not have permission to get URL / from this server

The Cloud Run service requires authentication and the caller has no valid identity token or the `roles/run.invoker` role.

Cloud Run: Image not found / failed to pullGoogle Cloud / Firebase

Cloud Run: Revision 'svc-00005' is not ready — Image 'gcr.io/proj/app:latest' not found / Permission 'artifactregistry.repositories.downloadArtifacts' denied

Cloud Run cannot pull the container image — it doesn't exist, the tag is wrong, or the service identity lacks access to the regis…

BigQuery: Access Denied: Project: User does not have bigquery.jobs.create permissionGoogle Cloud / Firebase

BigQuery: Access Denied: Project my-project: User does not have bigquery.jobs.create permission in project my-project

The principal can read data but is not allowed to run query jobs in the project used for billing.