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

# "Unable to allocate CIDR from the pool" error

When you create a Managed Service for Kubernetes® cluster, it may get stuck in the `Provisioning` status with the following error:

```text theme={null}
"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](#quota-for-ip-addresses-is-exceeded)
* [Selected subnet is too small](#selected-subnet-is-too-small)
* [CIDR block is too large](#cidr-block-is-too-large)

## Quota for IP addresses is exceeded

You may not have enough free [quota](../../vpc/resources/quotas-limits) for the IP addresses the cluster requires.

To find out if that is the case, get and compare the following information:

* See the complete list of required allocations in [Network requirements for Managed Service for Kubernetes® clusters](../networking/requirements).
* Check your free quota on the [Administration → Limits → Quotas](https://console.nebius.com/quotas) page in the web console.

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](../../vpc/overview#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:

* See the complete list of required allocations in [Network requirements for Managed Service for Kubernetes® clusters](../networking/requirements).
* Get the subnet metadata:

  ```bash theme={null}
  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.

To fix this, use one of the following solutions:

* Add a [pool](../../vpc/overview#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:

  ```bash theme={null}
  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](../../vpc/overview#pool) with more CIDR blocks to the subnet.
* Use another, larger subnet for your cluster.