Cloud and containers
Enable dual-stack or IPv6-only networking in a public-cloud VPC/VNet. Run a dual-stack Kubernetes cluster and reach a service over IPv6. Configure IPv6 in Docker.
Take the quiz · pass mark 70% · 9 questions
Explanation
Cloud and container platforms were historically IPv4-first, so IPv6 there is mostly about turning it on correctly and knowing each platform's model. There is no single standard to cite here; follow each vendor's current documentation, and verify the version because these features move quickly.
Public-cloud VPC/VNet
Each major cloud assigns IPv6 to a virtual network (VPC/VNet) differently, but the pattern is the same: the provider gives the VPC an IPv6 block, you enable IPv6 on subnets, instances get a global IPv6 address, and you must open the security groups / NSGs / firewall for IPv6 separately from IPv4 — a very common mistake is enabling IPv6 addressing but leaving the firewall IPv4-only, so IPv6 is either unreachable or (worse) wide open. Decide dual-stack vs IPv6-only per subnet; IPv6-only subnets with provider NAT64/DNS64 remove the IPv4 cost but need the translation path. Routing, egress and any load balancer must each be IPv6-enabled too.
Kubernetes dual-stack
Kubernetes supports dual-stack clusters: Pods and Services can have both an IPv4 and an IPv6 address. Key points: the cluster is configured with both a Pod CIDR and a Service CIDR per family; a Service's ipFamilyPolicy controls whether it is single- or dual-stack and ipFamilies sets the order; and the CNI plugin must support dual-stack. Typically each node gets a slice of the Pod CIDR (often a /64-per-node or similar) so Pods on a node share that prefix. Validate by resolving and connecting to a Service over IPv6 from inside and outside the cluster, and check that NetworkPolicy covers both families.
Docker
Docker can run IPv6 on its networks: enable IPv6 on the daemon/network and assign the network an IPv6 subnet. For a self-contained host a ULA subnet (from the fc00::/7 ULA block) is common for container-to-container traffic, with published ports or an IPv6-capable reverse proxy for ingress; for globally reachable containers use a routed global prefix. As with cloud, the host firewall must permit the container IPv6 traffic you intend and block the rest.
ictNetworks scenario
ictNetworks runs its platform on a dual-stack VPC with IPv6 explicitly allowed in the security groups (not just addressed), a dual-stack Kubernetes cluster whose Services are reachable over IPv6 and whose NetworkPolicy covers both families, and Docker hosts using a ULA (fc00::/7) for inter-container traffic behind an IPv6-capable proxy. Its checklist flags the classic trap of "IPv6 addressed but firewall IPv4-only" in every environment.
Drawing diagram…
Worked examples
Example 1: Pods per node CIDR
If each node is given a /56 slice of the Pod CIDR and Pods take /64s within it, the node can host 2^(64-56) = 256 /64 Pod subnets — far more than a node's Pod density, so the Pod CIDR, not the node slice, is the planning constraint.
Example 2: Address families on a dual-stack Service
A dual-stack Kubernetes Service carries 2 IP families (one IPv4 and one IPv6 ClusterIP), so clients can reach it over either protocol; ipFamilyPolicy and ipFamilies control this.
Example 3: The container ULA block
A self-contained Docker host commonly numbers its container network from the ULA block fc00::/7 for container-to-container traffic, exposing services through published ports or an IPv6-capable proxy.
Lab
Goal: Deploy a dual-stack Kubernetes service and reach it over IPv6.
You need: a dual-stack kind cluster (or a cloud free tier), a dual-stack-capable CNI, Docker with IPv6 enabled, and kubectl/curl. (All of kind, the CNI, Docker and any cloud console vary by version — follow current docs.)
- Enable IPv6 on a Docker network (assign a ULA subnet) and reach one container from another over IPv6.
- Create a dual-stack kind cluster (IPv4+IPv6 Pod and Service CIDRs) with a dual-stack CNI.
- Deploy a Deployment and a dual-stack Service (
ipFamilyPolicy: PreferDualStack); confirm it has both ClusterIPs. - Reach the Service over IPv6 from inside the cluster and (where possible) from the host; verify with
curl -6. - Apply a NetworkPolicy and confirm it is enforced for both families (a common gap).
What to submit: the Docker/kind/CNI configuration, the dual-stack Service showing both ClusterIPs, the IPv6 curl success, and the NetworkPolicy both-family result.
Summary
- Cloud/container IPv6 is mostly correct enablement; follow current vendor docs and verify the version.
- Enable IPv6 in the VPC/VNet and open the security group/NSG for IPv6 explicitly; choose dual-stack vs IPv6-only per subnet.
- Kubernetes dual-stack gives Pods/Services both families via the CNI and
ipFamilyPolicy; cover both in NetworkPolicy. - Docker runs IPv6 on its networks (often a ULA from fc00::/7); the host firewall must match intent.
- Next lesson (L7.07): public services over IPv6 (DNS, web, mail, load balancers).
Quiz imported · 9 questions · pass mark 70%. Lab questions are not auto-marked.