01
Insufficient allocatable CPU
The cluster may have physical CPU available while Kubernetes reservations and running workloads leave too few allocatable cores.
Akash provider troubleshooting
Your Akash provider does not have enough available capacity for the workload.
An Akash provider can advertise compatible resources but still reject a workload when current deployments, Kubernetes reservations or stale inventory leave too little allocatable capacity.
Run the free provider checkAvailable provider capacity
Why an Akash provider reports insufficient capacity
The provider must have enough currently allocatable CPU, memory, storage and specialized hardware to satisfy the complete deployment request.
02
Insufficient available memory
Existing deployments, system services and reserved memory may prevent the provider from satisfying a new workload.
03
Storage capacity is exhausted
The requested storage class may exist but have too little free persistent or ephemeral space remaining.
04
GPU resources are already allocated
Compatible GPUs may be installed and advertised while current leases have already reserved the available devices.
05
Kubernetes requests and limits reserve capacity
Pod requests, limits, DaemonSets and system workloads can reduce the resources available for tenant deployments.
06
Provider inventory is stale
The provider may advertise capacity that no longer matches current Kubernetes nodes, reservations or hardware availability.
Free diagnosis
What to check when available capacity is too low
Compare the workload request with Kubernetes allocatable resources, active reservations, running deployments, storage capacity and advertised provider inventory.
+Read the complete workload request
Record the requested CPU, memory, storage, GPU and replica quantities.
Record the requested CPU, memory, storage, GPU and replica quantities.
+Check Kubernetes allocatable resources
Compare node capacity with allocatable CPU, memory and specialized hardware.
Compare node capacity with allocatable CPU, memory and specialized hardware.
+Review running workload reservations
Identify resources already committed through pod requests, limits and active leases.
Identify resources already committed through pod requests, limits and active leases.
+Check storage availability
Verify each required storage class has enough unallocated capacity.
Verify each required storage class has enough unallocated capacity.
+Compare provider inventory
Confirm advertised resources match the current cluster and hardware state.
Confirm advertised resources match the current cluster and hardware state.
+Submit the capacity evidence
Use the free checker and include the workload request, provider decline message and current resource totals.
Use the free checker and include the workload request, provider decline message and current resource totals.
Start with evidence
Find the exact capacity shortage first
Run the free check, review the results and submit the failed items when you need help diagnosing lease declines or provider readiness.
Run the free Akash provider check