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 , 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 2001:db8::/56 then the syntax /64#a would mean .

Managed private and public subnets which have IPv6CIDR assignments route 64:ff9b::/96 (NAT64) to whatever is specified in the field of the subnet’s spec, defaulting the availability zone’s NAT Gateway.

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.

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

CNIs must not masquerade IPv6 addresses.

Running IPv6 with Calico requires a Debian 11-based AMI. As of the writing of this document, Ubuntu does not work due to an issue with systemd’s handling of AWS’s incorrect DHCP responses.

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