From 5905170d8ab61aa3687138a54dea60675667dad0 Mon Sep 17 00:00:00 2001 From: nevermyuk Date: Thu, 23 Apr 2020 19:49:54 +0800 Subject: [PATCH] Add note to Flannel Preparation Step Add note to Flannel Preparation Step Remove note remove whitespace remove whitespace --- .../tasks/administer-cluster/kubeadm/adding-windows-nodes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md b/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md index f6d58c87c4..1195456547 100644 --- a/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md +++ b/content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md @@ -48,7 +48,7 @@ Once you have a Linux-based Kubernetes control-plane node you are ready to choos 1. Prepare Kubernetes control plane for Flannel - Some minor preparation is recommended on the Kubernetes control plane in our cluster. It is recommended to enable bridged IPv4 traffic to iptables chains when using Flannel. This can be done using the following command: + Some minor preparation is recommended on the Kubernetes control plane in our cluster. It is recommended to enable bridged IPv4 traffic to iptables chains when using Flannel. The following command must be run on all Linux nodes: ```bash sudo sysctl net.bridge.bridge-nf-call-iptables=1