From 1f25844a8a17ddeeba3b68330b5a5c199566fbcb Mon Sep 17 00:00:00 2001 From: Manuel Buil Date: Fri, 22 Apr 2022 14:21:04 +0200 Subject: [PATCH] Update ipv6-only docs Signed-off-by: Manuel Buil --- .../k3s/latest/en/installation/network-options/_index.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/k3s/latest/en/installation/network-options/_index.md b/content/k3s/latest/en/installation/network-options/_index.md index c667a7cef73..652f22f6adc 100644 --- a/content/k3s/latest/en/installation/network-options/_index.md +++ b/content/k3s/latest/en/installation/network-options/_index.md @@ -89,10 +89,8 @@ If you are using a custom cni plugin, i.e. a cni plugin different from flannel, ### IPv6 only installation -IPv6 only setup is supported on k3s v1.22 or above. As in dual-stack operation, IPv6 node addresses cannot be auto-detected; all nodes must have an explicitly configured IPv6 `node-ip`. This is an example of a valid configuration: +IPv6 only setup is supported on k3s v1.22 or above. Note that network policy enforcement is not supported on IPv6-only clusters when using the default flannel CNI. This is an example of a valid configuration: ``` -k3s server --node-ip 2a05:d012:c6f:4611:5c2:5602:eed2:898c --cluster-cidr 2001:cafe:42:0::/56 --service-cidr 2001:cafe:42:1::/112 +k3s server --disable-network-policy ``` - -Note that you can specify only one IPv6 `cluster-cidr` value.