From a6959fdf4ac6c52a09b21a791d3a1e9fdf03dc17 Mon Sep 17 00:00:00 2001 From: Manuel Buil Date: Fri, 10 Jun 2022 13:06:24 +0200 Subject: [PATCH] Update the ipv6 information 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 652f22f6adc..138a0618713 100644 --- a/content/k3s/latest/en/installation/network-options/_index.md +++ b/content/k3s/latest/en/installation/network-options/_index.md @@ -89,8 +89,6 @@ 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. 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: +IPv6 only setup is supported on k3s v1.22 or above -``` -k3s server --disable-network-policy -``` +> **Warning:** If your IPv6 default route is set by a router advertisement (RA), you will need to set `net.ipv6.conf.all.accept_ra = 2`; otherwise, the node will drop the default route once it expires. Be aware that accepting RAs could increase the risk of [man-in-the-middle attacks](https://github.com/kubernetes/kubernetes/issues/91507).