IPv6

IPv6 mode is specified by setting in the cluster spec. The --ipv6 flag of kops create cluster sets this field, among others.

kOps currently supports IPv6 on AWS only.

IPv6 requires the external Cloud Controller Manager.

Subnet IPv6 CIDR allocations may be specified in the cluster spec using the special syntax /LEN#N, where “LEN” is the prefix length and “N” is the hexadecimal sequence number of the CIDR within the VPC’s IPv6 CIDR. For example, if the VPC’s CIDR is then the syntax /64#a would mean 2001:db8:0:a/64.

Public and utility subnets are expected to be dual-stack. Subnets of type Private are expected to be IPv6-only. There is a new type of subnet which is like Private but is dual-stack. The DualStack subnets are used by default for the control plane and APIServer nodes.

IPv6-only subnets require Kubernetes 1.22 or later. For this reason, private topology on an IPv6 cluster also requires Kubernetes 1.22 or later.

If a NAT Gateway is thus needed by a managed public subnet and there are no utility subnets in that availability zone, the NAT Gateway will be placed in the first-listed public subnet in that zone.

The managed private subnets route the rest of outbound IPv6 traffic to the VPC’s Egress-only Internet Gateway. The managed public subnets route the rest of outbound IPv6 traffic to the VPC’s Internet Gateway.

kOps currently supports IPv6 on Calico, Cilium, and bring-your-own CNI only.

Running IPv6 with Calico requires a Debian 11 or Ubuntu 22.04 based AMI.

• External-DNS does not, as of the writing of this document, support registering AAAA records.