# Limitations

Following are a few limitations that you can encounter while using both **Public** and **Private Node Pools**:

* The maximum number of pods supported per node is **110**. It is a Kubernetes default value.
* The recommended maximum number of nodes per node pool is **20**.
* The maximum number of nodes in a node pool is **100**.
* A total of **500** node pools per cluster is supported.
* The recommended maximum number of node pools per cluster are **50**.
* The maximum number of supported nodes per cluster is **5000**.
* While a node can theoretically support a maximum of **20** volumes, the practical limit can be lower because each node has only 24 PCI slots shared among all peripherals.

## Private Node Pools

Following are a few limitations that you can encounter while using **Private Node Pools**:

* Managed Kubernetes clusters for Private Node Pools are bound to **one region**. When you create a node pool, you need to provide a data center, which has to be in the same location as defined in the **cluster**. You can create Private Node Pools only in a see [<mark style="color:blue;">Virtual Data Center (VDC)</mark>](https://docs.ionos.com/cloud/support/general-information/glossary-of-terms#virtual-data-center-vdc) that shares the region with the managed Kubernetes cluster.
* Kubernetes services of type **LoadBalancer** are currently not supported.
* The **static node Internet Protocol (IP)** addresses are not supported.