/
_networking-vsphere.html.md.erb
35 lines (32 loc) · 2.26 KB
/
_networking-vsphere.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
To configure networking, do the following:
1. Click **Networking**.
<% if current_page.data.windowsclusters == true %>
1. Under **Container Networking Interface**, select:
* **NSX** for Windows worker based clusters on vSphere with NSX.
* **Flannel** for Windows worker based clusters on vSphere without NSX beta.
<img src="images/networking-flannel-2.png" alt="Networking pane configuration" width="425">
<p class="note"><strong>Note</strong>:
Antrea is not supported for the <%= vars.k8s_runtime_abbr %> Windows-worker on vSphere without NSX beta feature.</p>
1. (Optional) Enter values for **Kubernetes Pod Network CIDR Range** and **Kubernetes Service Network CIDR Range**.
* For Windows worker-based clusters the **Kubernetes Service Network CIDR Range** setting must be `10.220.0.0/16`.
<p class="note"><strong>Note:</strong> vSphere on Flannel does not support networking Windows containers.
</p>
<% else %>
1. Under **Container Networking Interface**, select **Antrea**.
<img src="images/networking-antrea.png" alt="Networking pane configuration" width="425">
Antrea is selected as the default Container Networking Interface (CNI). <%= vars.recommended_by %> recommends that you use Antrea
as your CNI.
<p class="note">
<strong>Note:</strong> Support for the Flannel Container Networking Interface (CNI) is deprecated.
<%= vars.recommended_by %> recommends that you switch your Flannel CNI-configured clusters to the Antrea CNI.
For more information about Flannel CNI deprecation, see
<a href="understanding-upgrades.html#cni">About Switching from the Flannel CNI to the Antrea CNI</a>
in <i>About <%= vars.product_short %> Upgrades</i>.
</p>
1. (Optional) Enter values for **Kubernetes Pod Network CIDR Range** and **Kubernetes Service Network CIDR Range**.
* Ensure that the CIDR ranges do not overlap and have sufficient space for your deployed services.
* Ensure that the CIDR range for the **Kubernetes Pod Network CIDR Range** is large enough to accommodate the expected maximum number of pods.
<% end %>
<%= partial 'global-proxy' %>
1. Under **Allow outbound internet access from Kubernetes cluster vms (IaaS-dependent)**, ignore the **Enable outbound internet access** check box.
1. Click **Save**.