From e3a7a56878516820ddc9daa3285388d5c170357c Mon Sep 17 00:00:00 2001 From: wawa Date: Fri, 17 Jan 2020 23:54:59 +0800 Subject: [PATCH] Remove redundant information when deploy flannel on kubernetes include windows node (#18274) --- .../windows/user-guide-windows-nodes.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/content/en/docs/setup/production-environment/windows/user-guide-windows-nodes.md b/content/en/docs/setup/production-environment/windows/user-guide-windows-nodes.md index 399bd54fb8..297ec97d79 100644 --- a/content/en/docs/setup/production-environment/windows/user-guide-windows-nodes.md +++ b/content/en/docs/setup/production-environment/windows/user-guide-windows-nodes.md @@ -140,12 +140,6 @@ Once you have a Linux-based Kubernetes control-plane ("Master") node you are rea kubectl apply -f kube-flannel.yml ``` - Next, since the Flannel pods are Linux-based, apply a NodeSelector patch, which can be found [here](https://github.com/Microsoft/SDN/blob/1d5c055bb195fecba07ad094d2d7c18c188f9d2d/Kubernetes/flannel/l2bridge/manifests/node-selector-patch.yml), to the Flannel DaemonSet pod: - - ```bash - kubectl patch ds/kube-flannel-ds-amd64 --patch "$(cat node-selector-patch.yml)" -n=kube-system - ``` - After a few minutes, you should see all the pods as running if the Flannel pod network was deployed. ```bash