Chapter 4. IP Address Management
Before deploying Cilium in a Kubernetes cluster, platform engineers need to make two fundamental networking decisions: how pod IP addresses are allocated, and whether to use IPv4, IPv6, or both. Selecting the right IP address management mode is essential, as changing it later may disrupt connectivity for running workloads or may not be supported at all.
Broader organizational requirements typically drive the choice between IPv4, IPv6, or dual stack, but the options also demand careful consideration by platform teams during initial cluster design. This chapter will help you make an informed decision. We will start by examining the different IPAM modes supported by Cilium and highlighting the pros and cons of each. We will then explore the dual stack and IPv6 deployment models. Sample manifests are included for you to try in your own test environments; you can find all the YAML manifests in the chapter04 directory of the book’s GitHub repository.
IPv4 and IPv6 Support in Cilium
We’ll start with a brief overview of IPv4 and IPv6 support before we explain how IP addresses are assigned and how pods communicate with each other. Kubernetes supports single-stack IPv4, single-stack IPv6, and dual-stack networking, depending on the CNI you choose to implement the required functionality.
With single-stack IPv4/IPv6 networking, each pod and service can be assigned a single IPv4 or IPv6 address. With dual-stack networking, each pod and service can be assigned ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access