From 3f4883d593b49e0419ae7a17f256258d65a8f0aa Mon Sep 17 00:00:00 2001 From: Roberto Bonafiglia Date: Fri, 18 Mar 2022 11:46:42 +0100 Subject: [PATCH] Update K3s network installation doc --- .../en/installation/network-options/_index.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/content/k3s/latest/en/installation/network-options/_index.md b/content/k3s/latest/en/installation/network-options/_index.md index 78e734929ea..2ceeaa9a2f8 100644 --- a/content/k3s/latest/en/installation/network-options/_index.md +++ b/content/k3s/latest/en/installation/network-options/_index.md @@ -74,6 +74,8 @@ You should see that IP forwarding is set to true. Dual-stack networking must be configured when the cluster is first created. It cannot be enabled on an existing single-stack cluster. +Dual-stack is supported on k3s v1.21 or above. + To enable dual-stack in k3s, you must provide valid dual-stack `cluster-cidr` and `service-cidr`, and set `disable-network-policy` on all server nodes. Both servers and agents must provide valid dual-stack `node-ip` settings. Node address auto-detection and network policy enforcement are not supported on dual-stack clusters when using the default flannel CNI. Besides, only vxlan backend is supported at the moment. This is an example of a valid configuration: ``` @@ -86,3 +88,18 @@ disable-network-policy: true Note that you can choose whatever `cluster-cidr` and `service-cidr` value, however the `node-ip` values must correspond to the ip addresses of your main interface. Remember to allow ipv6 traffic if you are deploying in a public cloud. If you are using a custom cni plugin, i.e. a cni plugin different from flannel, the previous configuration might not be enough to enable dual-stack in the cni plugin. Please check how to enable dual-stack in its documentation and verify if network policies can be enabled. + +### IPv6 only installation + +IPv6 only setup is supported on k3s v1.22 or above. + +IPv6 only setup requires a similar setup as dual-stack where you must provide a valid IPv6 `node-ip` on both servers and agents. This is an example of a valid configuration: + +``` +node-ip: 2a05:d012:c6f:4611:5c2:5602:eed2:898c +cluster-cidr: 2001:cafe:42:0::/56 +service-cidr: 2001:cafe:42:1::/112 +disable-network-policy: true +``` + +Note that you can specify only one IPv6 `cluster-cidr` value.