Skip to main content
When you create a Managed Service for Kubernetes® cluster, it may get stuck in the Provisioning status with the following error: 
"rpc error: code = FailedPrecondition desc = Unable to allocate private
ipv4 cidr /32 from the pool. Please verify the availability of the cidrs
and retry the allocation."
This error usually indicates that there is not enough CIDR space available for IP address allocation. Possible causes:

​
Quota for IP addresses is exceeded

You may not have enough free quota for the IP addresses the cluster requires. To find out if that is the case, get and compare the following information: To fix this, use one of the following solutions:
  • Remove unused resources to free up quota.
  • Request a quota increase on the Administration → Limits → Quotas page.

​
Selected subnet is too small

The subnet you specified during cluster creation may not have enough CIDR blocks. To find out if that is the case, get and compare the following information: To fix this, use one of the following solutions:
  • Add a pool with more CIDR blocks to the subnet.
  • Use another, larger subnet for your cluster.

​
CIDR block is too large

If you specified a CIDR block for Kubernetes services that is too large, no free blocks for other control plane requirements may be left in the subnet. To find out if that is the case, get and compare the following information:
  • Get the subnet metadata: 
    nebius vpc subnet get --id <subnet_ID>
    To find the available CIDR blocks, check the cidr values in the spec.ipv4_private_pools.pools.cidrs list in the response.
  • Check the value of the spec.kube_network.service_cidrs parameter that you set during cluster creation.
To fix this, use one of the following solutions:
  • Specify a smaller block for services in the spec.kube_network.service_cidrs parameter.
  • Add a pool with more CIDR blocks to the subnet.
  • Use another, larger subnet for your cluster.