View quotas
To view your resource quotas, log in to your CoreWeave organization on the Cloud Console and go to the Quotas page. On this page, you can browse quotas or search for a specific one.
How quotas apply to instance types
Quotas apply per organization, per instance type, per compute class, per zone. Compute class is the Node Pool’s tier, eitherdefault or spot (preemptible), so a default Node Pool and a spot Node Pool of the same instance type and zone count against separate quotas. For example, in the same zone, gd-8xh100ib-i128 at default compute class and the same instance type at spot are tracked as two separate quotas with independent limits. CKS checks the quota every time targetNodes is set, whether you’re creating a new Node Pool or scaling an existing one. If a request exceeds the quota, CKS fills the Node Pool only up to the allowed amount and does not queue the remainder.
To identify the instance types your organization uses, see GPU instances and CPU instances. To check which instance types are offered in each zone, see the Availability matrix.
To check the quota status of a Node Pool, run kubectl get nodepool and read the QUOTA column, or run kubectl describe nodepool [NODE-POOL-NAME] and read the Quota condition. An Over status means the Node Pool’s targetNodes exceeds your organization’s quota for that instance type, compute class, and zone. For the full meaning of each status, see Node Pool conditions: Quota.
Quota errors
When a Node Pool’stargetNodes request reaches a quota limit, the Node Pool controller emits a Kubernetes event. The bottom of kubectl describe nodepool [NODE-POOL-NAME] lists recent events. For example:
Example output
For the complete event schema, see the Node Pool reference: Events. For troubleshooting quota and capacity states together, see Node Pool status: Common capacity and quota states.