whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix links in windows-nodes, runtimeClass (#13486)

Browse Source
This commit is contained in:
Karen Bradshaw
2019-03-27 23:34:44 -04:00
committed by Kubernetes Prow Robot
parent 4fd724ba09
commit 91ac5c6044
2 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/containers/runtime-class.md
+1 -1
View File
@@ -41,7 +41,7 @@ feature gates. The `RuntimeClass` feature gate must be enabled on apiservers _an
#### 1. Configure the CRI implementation on nodes
The configurations available through RuntimeClass are Container Runtime Interface (CRI)
implementation dependent. See the corresponding documentation ([below](#cri-documentation)) for your
implementation dependent. See the corresponding documentation ([below](#cri-configuration)) for your
CRI implementation for how to configure.
{{< note >}}
content/en/docs/setup/windows/user-guide-windows-nodes.md
+2 -3
View File
@@ -88,9 +88,8 @@ Once you have a Linux-based Kubernetes master node you are ready to choose a net
}
```
{{< note >}}
The VNI must be set to 4096 and port 4789 for Flannel on Linux to interoperate with Flannel on Windows. Support for other VNIs is coming soon. See the VXLAN documentation at https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan for an explanation of these fields.
{{< /note >}}
{{< note >}}The VNI must be set to 4096 and port 4789 for Flannel on Linux to interoperate with Flannel on Windows. Support for other VNIs is coming soon. See the [VXLAN documentation](https://github.com/coreos/flannel/blob/master/Documentation/backends.md#vxlan)
for an explanation of these fields.{{< /note >}}
1. In the `net-conf.json` section of your `kube-flannel.yml`, double-check:
1. The cluster subnet (e.g. "10.244.0.0/16") is set as per your IP plan.