_networking-vsphere.html.md.erb

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.  
    <p class="note"><strong>Note</strong>: 
      Antrea is not supported for the TKGI 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`.  
<% else %>
1. Under **Container Networking Interface**, select **Antrea**.  
    <img src="images/networking-antrea.png" alt="Networking pane configuration" width="425">
    Antrea is the Container Networking Interface (CNI) for TKGI <%= vars.product_version %>. Flannel CNI is no longer supported.
    For more information about Flannel CNI removal, see 
    <a href="https://docs.vmware.com/en/VMware-Tanzu-Kubernetes-Grid-Integrated-Edition/1.18/tkgi/GUID-understanding-upgrades.html#upgrade-the-cni">About Switching from the Flannel CNI to the Antrea CNI</a> in the TKGI 1.18 documentation.
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**.