> ## Documentation Index
> Fetch the complete documentation index at: https://docs.coreweave.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why are my Pods not scheduling on GPU Nodes?

GPU Pods stay `Pending` when they request a resource the available GPU Nodes do not provide, when no Node Pool of the requested instance type has capacity, or when the Pod's `nodeSelector` or tolerations do not match any Node. Run `kubectl describe pod [POD-NAME]` and read the events at the bottom. The scheduler logs the exact mismatch (for example, `0/3 nodes are available: 3 Insufficient nvidia.com/gpu`).

Common causes and fixes:

* **No Node has enough GPUs**: lower the `nvidia.com/gpu` request, or add or scale a [Node Pool](/products/cks/nodes/nodes-and-node-pools) of the right instance type. See [What is the autoscaler behavior when Pods are pending?](/support/cks/articles/what-is-the-autoscaler-behavior-when-pods-are-pending).
* **`nodeSelector` doesn't match any Node**: correct the selector to match the labels actually present on your Nodes. See [How do I request specific GPU types using node selectors?](/support/cks/articles/how-do-i-request-specific-gpu-types-using-node-selectors).
* **Tolerations don't match Node taints**: confirm your Pod tolerates the correct [user taints](/products/cks/clusters/scheduling/workload-scheduling#user-taints) for the hardware you target.
* **Resource quota exceeded**: check your namespace quota. See [How do I check my resource quota?](/support/cks/articles/how-do-i-check-my-resource-quota).

For full details on Node labels and taints, see [Workload scheduling on CKS](/products/cks/clusters/scheduling/workload-scheduling).

***

<Badge stroke shape="pill" color="blue" size="md">[Workload Scheduling](/support/cks/tags/workload-scheduling)</Badge><Badge stroke shape="pill" color="blue" size="md">[Server Errors](/support/cks/tags/server-errors)</Badge>