From 5242e397b7227320c7795c79a0a0db911db64d05 Mon Sep 17 00:00:00 2001 From: Tejeev Date: Tue, 10 Aug 2021 16:12:46 +0100 Subject: [PATCH] Should dissable IPv6 --- .../v2.5/en/cluster-provisioning/node-requirements/_index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/rancher/v2.5/en/cluster-provisioning/node-requirements/_index.md b/content/rancher/v2.5/en/cluster-provisioning/node-requirements/_index.md index 1ab8a565fcf..ba493fa05f2 100644 --- a/content/rancher/v2.5/en/cluster-provisioning/node-requirements/_index.md +++ b/content/rancher/v2.5/en/cluster-provisioning/node-requirements/_index.md @@ -102,6 +102,8 @@ For hardware recommendations for etcd clusters in production, refer to the offic For a production cluster, we recommend that you restrict traffic by opening only the ports defined in the port requirements below. +IPv6 should be dissabled at the OS level. Unless you specifically intend to utilize IPv6, you should dissable it on you rnodes. IPv6 is not yet fully supported and often times it is not enough to dissable ipv6 on the NICs to avoid complications. + The ports required to be open are different depending on how the user cluster is launched. Each of the sections below list the ports that need to be opened for different [cluster creation options]({{}}/rancher/v2.5/en/cluster-provisioning/). For a breakdown of the port requirements for etcd nodes, controlplane nodes, and worker nodes in a Kubernetes cluster, refer to the [port requirements for the Rancher Kubernetes Engine.]({{}}/rke/latest/en/os/#ports)