IPv6 NetworksEnterpriseSelf-Hosted
Okteto runs in IPv6-only and dual-stack Kubernetes clusters. IPv6 support is available in Okteto chart version 1.51 and later. Some components require you to enable IPv6 explicitly in your Okteto Helm configuration.
Network Requirements
The pods that Okteto runs in your cluster need to reach your Git provider and your container registries: the installer jobs clone your repositories, the Okteto Build Service pulls base images, and your application environments pull their images.
Some providers, like GitHub (github.com and ghcr.io), don't have IPv6 addresses. In IPv6-only clusters, give your pods access to IPv4 destinations through NAT64 and DNS64, or through an HTTP proxy.
Helm Configuration
Add the following to your Okteto Helm configuration:
buildkit:
network:
ipv6:
enabled: true
If you enabled network policies (networkPolicies.enabled: true), also enable IPv6 in them:
networkPolicies:
enabled: true
ipv6:
enabled: true
BuildKit Network and Network Policies describe what each setting does.
BuildKit Network
The Okteto Build Service runs your Dockerfiles' RUN instructions in an isolated network, separate from the BuildKit pod's network. This network is IPv4-only by default (10.10.0.0/16), so in IPv6-only clusters the RUN instructions can't reach your cluster DNS, the Okteto API, or the internet.
This also affects Remote Execution: the Okteto CLI runs your deploy and destroy commands inside a RUN instruction, and they fail with Internal server error if that network has no IPv6.
buildkit.network.ipv6.enabled adds an IPv6 subnet (fdbd:6b1d:2c0e::/64 by default) to the RUN instructions' network.
In IPv6-only clusters, you can also disable the IPv4 subnet. Change the subnets if they overlap with networks your builds need to reach:
buildkit:
network:
ipv4:
enabled: false
ipv6:
enabled: true
subnet: fd12:3456:789a::/64
When BuildKit runs in rootless mode, the RUN instructions use the BuildKit pod's network, which already has IPv6 in IPv6 and dual-stack clusters. These settings don't apply in rootless mode.
Network Policies
This setting only applies when network policies are enabled. With network policies, Okteto allows egress traffic to 0.0.0.0/0, except to networkPolicies.blockedCIDRs. Without networkPolicies.ipv6.enabled, the network policies block all IPv6 egress traffic from your Namespaces, the installer jobs, and BuildKit.
networkPolicies.ipv6.enabled also allows egress traffic to ::/0, except to networkPolicies.ipv6.blockedCIDRs. By default, it blocks the IPv6 address of the AWS instance metadata service:
networkPolicies:
enabled: true
blockedCIDRs:
- "169.254.169.254/32"
ipv6:
enabled: true
blockedCIDRs:
- "fd00:ec2::254/128"
networkPolicies.blockedCIDRs only accepts IPv4 CIDRs. Add IPv6 CIDRs to networkPolicies.ipv6.blockedCIDRs.