You shut down the components of a VI workload domain that runs containerized workloads in VMware Cloud Foundation in a specific order to keep components operational by maintaining the necessary infrastructure, networking, and management services as long as possible before shutdown.
You shut down the management components for the VI workload domains that run vSphere with Tanzu and containers or that run virtualized workloads before you shut down the components for the management domain.
If the NSX Manager cluster and NSX Edge cluster are shared with other VI workload domains, follow this general order:
Shut down the customer workloads in all VI workload domains that share the NSX instance. Otherwise, all NSX networking services in the customer workloads will be interrupted when you shut down NSX.
Shut down the VI workload domain that runs the shared NSX Edge nodes.
Shut down the other VI workload domains.
Shutdown Order for a VI Workload Domain with vSphere with Tanzu
Shutdown Order |
SDDC Component |
---|---|
1 |
Containerized customer workloads |
2 |
Find out the location of the vSphere with Tanzu virtual machines * |
3 |
vSphere Cluster Services virtual machines in the VI workload domain * |
4 |
vCenter Server for the VI workload domain * |
5 |
|
6 |
|
7 |
|
8 |
|
9 |
NSX Edge nodes in the VI workload domain * |
10 |
NSX Manager nodes for the VI workload domain * |
11 |
vSAN and ESXi hosts in the VI workload domain * |
* For information on the shutdown steps, see below.
Find Out the Location of the vSphere with Tanzu Virtual Machines on the ESXi Hosts
Before you begin shutting down a VI workload domain with vSphere with Tanzu, you get a mapping between virtual machines in the workload domain and the ESXi hosts on which they are deployed. You later use this mapping to log in to specific ESXi hosts and shut down specific management virtual machines.
Procedure
Shut Down the vSphere Cluster Services Virtual Machines
To shut down the vSphere Cluster Services (vCLS) virtual machines in a cluster in a VI workload domain in VMware Cloud Foundation, you put the cluster in retreat mode. The retreat mode triggers clean-up of the vCLS virtual machines.
Procedure
Results
The vCLS monitoring service initiates the clean-up of vCLS VMs. If vSphere DRS is activated for the cluster, it stops working and you see an additional warning in the cluster summary. vSphere DRS remains deactivated until vCLS is re-activated on this cluster.
Shut Down vCenter Server for a Virtual Infrastructure Workload Domain with vSphere with Tanzu
To shut down the vCenter Server instance for a VI workload domain with vSphere with Tanzu in VMware Cloud Foundation, you use the vSphere Client. You stop the Kubernetes services and check the vSAN health status.
Procedure
Shut Down the NSX Edge Nodes for vSphere with Tanzu
You begin shutting down the NSX infrastructure in a VI workload domain with vSphere with Tanzu by shutting down the NSX Edge nodes that provide north-south traffic connectivity between the physical data center networks and the NSX SDN networks.
Because the vCenter Server instance for the domain is already down, you shut down the NSX Edge nodes from the ESXi hosts where they are running.
Procedure
- Log in to the ESXi host that runs the first NSX Edge node as root by using the VMware Host Client.
- In the navigation pane, click Virtual machines.
- Right-click an NSX Edge virtual machine, and select
- In the confirmation dialog box, click Yes.
- Repeat these steps to shut down the remaining NSX Edge nodes for the VI workload domain with vSphere with Tanzu.
Shut Down the NSX Manager Nodes
You continue shutting down the NSX infrastructure for the management domain or for a VI workload domain by shutting down the three-node NSX Manager cluster by using the vSphere Client.
Procedure
Shut Down vSAN and the ESXi Hosts in a Virtual Infrastructure Workload Domain with vSphere with Tanzu
You shut down vSAN and the ESXi hosts in a VI workload domain with vSphere with Tanzu by preparing the vSAN cluster for shutdown, placing each ESXi host in maintenance mode to prevent any virtual machines being deployed to or starting up on the host, and shutting down the host.