Check out how to create vSphere Zones that you can use to provide cluster-level high availability to your Kubernetes workloads running on a Supervisor. To provide cluster-level high availability to your Kubernetes workloads, you deploy the Supervisor on three vSphere Zones. Each vSphere Zone is mapped to one vSphere cluster that has a minimum of 2 hosts.

Prerequisites

  • Create three vSphere clusters with at least 3 hosts in each zone. For storage with vSAN, the cluster must have 4 hosts. For test of POC environments, each cluster must have at least 1 hosts, and 2 hosts when using vSAN.

  • Configure storage with vSAN or other shared storage solution for each cluster.
  • Enable vSphere HA and vSphere DRS on Fully Automate or Partially Automate mode.
  • Configure networking with NSX or vSphere Distributed Switch (vDS) networking for the clusters.

Procedure

  1. In the vSphere Client, navigate to vCenter Server.
  2. Select Configure and select vSphere Zones.
  3. Click Add New vSphere Zone.
  4. Name the zone, for example zone1 and add an optional description.
  5. Select a vSphere cluster to add to the zone and click Finish.
  6. Repeat the steps to create three vSphere Zones.

What to do next

Managing vSphere Zones

If you need to make changes to a vSphere Zone, you have do that before you deploy a Supervisor on the zone. You can change the cluster that is associated with it, or delete the zone. Deleting a vSphere Zone removes its associated cluster and then deletes the zone from vCenter Server.

Removing a Cluster from a vSphere Zone

To remove a cluster from a vSphere Zone, click the three dots (…) on the zone card and select Remove Cluster. The cluster is removed from the zone and you can add a different one.

Note: You cannot remove a cluster from a vSphere Zone when there is a Supervisor already enabled on that zone.

Deleting a vSphere Zone

To delete a vSphere Zone, click the three dots (…) on the zone card and select Delete Zone.
Note: You cannot delete a vSphere Zone when there is a Supervisor already enabled on that zone.