IP Address Management (IPAM)

.. only:: not (epub or latex or html)

WARNING: You are looking at unreleased Cilium documentation.
Please use the official rendered version released here:
https://docs.cilium.io

.. _address_management:

IP Address Management (IPAM)

IP Address Management (IPAM) is responsible for the allocation and management of IP addresses used by network endpoints (container and others) managed by Cilium. Various IPAM modes are supported to meet the needs of different users:

============================ ====================== ======================== =========== =========== =============== ================= =============== Feature Kubernetes Host Scope Cluster Scope (default) Multi-Pool CRD-backed AWS ENI Azure IPAM GKE ============================ ====================== ======================== =========== =========== =============== ================= =============== Tunnel routing ✅ ✅ ✅ ❌ ❌ ❌ ❌ Direct routing ✅ ✅ ✅ ✅ ✅ ✅ ✅ CIDR Configuration Kubernetes Cilium Cilium External External (AWS) External (Azure) External (GCP) Multiple CIDRs per cluster ❌ ✅ ✅ N/A N/A N/A N/A Multiple CIDRs per node ❌ ❌ ✅ N/A N/A N/A N/A Dynamic CIDR/IP allocation ❌ ❌ ✅ ✅ ✅ ✅ ❌ ============================ ====================== ======================== =========== =========== =============== ================= ===============

Don't change the IPAM mode of an existing cluster except when following a documented migration procedure. Changing the IPAM mode in a live environment may cause persistent disruption of connectivity for existing workloads. The safest path to change IPAM mode is to install a fresh Kubernetes cluster with the new IPAM configuration.

The only currently available online migration path is from cluster-pool IPAM to multi-pool IPAM. To migrate, see :ref:ipam_cluster_pool_to_multi_pool_migration.

.. toctree:: :maxdepth: 1 :glob:

cluster-pool kubernetes multi-pool cluster-pool-to-multi-pool azure azure-delegated-ipam eni gke crd deep_dive