> For the complete documentation index, see [llms.txt](https://docs.cloudeka.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudeka.ai/guidance-for-enterprise/service-limit/crds/cloudeka-ippool.md).

# Cloudeka Ippool

An address pool your [Floating IPs](/guidance-for-enterprise/service-limit/crds/cloudeka-floating-ip.md) are allocated from — either `internet` (public IPs) or `local` (private ranges). Pools are set up and sized by the platform team; you consume from them, you don't create or resize pools yourself.

```bash
kubectl get cip -n <your-namespace>
kubectl get cip -n <your-namespace> -o yaml
```

<table><thead><tr><th width="206.16668701171875">Field</th><th>Meaning</th></tr></thead><tbody><tr><td><code>spec.purpose</code></td><td><code>internet</code> (public) or <code>local</code> (private)</td></tr><tr><td><code>spec.enable</code></td><td>Whether the pool is currently accepting new allocations</td></tr><tr><td><code>status.capacity</code></td><td>Total addresses in the pool</td></tr><tr><td><code>status.used</code></td><td>Addresses currently allocated</td></tr></tbody></table>

## When to check this

If a `Service` of type `LoadBalancer` is stuck without an `EXTERNAL-IP` for an unusually long time, check whether the relevant pool is near or at capacity (`status.used == status.capacity`) or disabled (`spec.enable: false`).

{% hint style="warning" %}
If the pool is at capacity or disabled, contact platform support — pool sizing is not something you can change yourself.
{% endhint %}