wcp-shutdown will gracefully shutdown a vSphere with Tanzu environment including Supervisor Cluster and all TKG Guest Clusters. The use case for the script is gracefully shutting down both Supervisor Cluster and Workload Clusters in a vSphere w/ Tanzu environment. Typically this is needed for planned maintenance to your vSphere environment such as a planned datacenter outage. Because of permissions issues with Supervisor Cluster Virtual Machines in vCenter you need to provide the script with both vCenter Credentials and local ESXi credentials.
- Find and Return 3 Supervisor Control Plane VMs from pyVmomi vSphere API.
- Find all TKG Workload Cluster Machine objects from K8s API on Supervisor Cluster.
- Shutdown WCP Service on vCenter and set Startup Type to Manual.
- Shutdown Supervisor Control Plane VMs - VC API or GOVC
- Shutdown all Worker & Control Plane Nodes in TKG Clusters - VC API or GOVC
- Cordon all Workload Cluster Worker Nodes - K8s API on GC
- Validate all Guest Clusters are powere down on Supervisor Cluster - K8s API
On Ubuntu 20.04 with Python3 already installed.
- Make sure kubectl with kubectl vSphere plugin installed on the Host
root# which kubectl
/usr/local/bin/kubectl
root# which kubectl-vsphere
/usr/local/bin/kubectl-vsphere
- Install the required Python Modules
pip3 install --force pyvmomi
pip3 install --force pyvim
pip3 install kubernetes
git clone https://github.com/tkrausjr/wcp-shutdown.git
You must run the script with a User that has permissions to shutdown Virtual Machines (Guest Operations). A member of the Administrators group on vCenter will work. ESxi credentials will also be needed to shutdown the Supervisor Control Pane Virtual Machines.
python3 wcp-shutdown.py --help usage: wcp-shutdown.py [-h] -v VC_HOST [-o PORT] -u VC_USER [-p VC_PASSWORD] [-e ESX_USER] [-f ESX_PASSWORD] [-c CLUSTER]
Script for shutting down Supervisor and Workload Clusters in vSphere w/ Tanzu
options: -h, --help show this help message and exit -v VC_HOST, --vc_host VC_HOST (Required) Remote VC host to connect to -o PORT, --port PORT (Optional) Port to connect on. Default=443. -u VC_USER, --vc_user VC_USER (Required) User name to use when connecting to vCenter. -p VC_PASSWORD, --vc_password VC_PASSWORD (Required) Password to use when connecting to vCenter. -e ESX_USER, --esx_user ESX_USER (Optional) User name to use when connecting to ESXi host. Default=root. -f ESX_PASSWORD, --esx_password ESX_PASSWORD (Optional) Password to use when connecting to ESXi host. If not provided user will be prompted to enter at runtime. -c CLUSTER, --cluster CLUSTER (Required) vSphere Cluster Name that vSphere with Tanzu is configured on.
To run the shutdown script
cd wcp-shutdown/
python3 wcp-shutdown.py -v 192.168.100.50 -u [email protected] -p <yourpassword> -c vsphere-cluster-1
Enter root password for ESXi hosts:
STEP 0 - Logging into vCenter API with supplied credentials
--Successfully logged in to VIM API
-Found a total of 11 VMS on VC.
-Found the vSphere Cluster named vsphere-cluster-1 with ID domain-c8
STEP 1 - Getting all Workload Cluster VMs from K8s API Server on Supervisor Cluster
-WCP Endpoint for SC is 192.168.104.11
Logged in successfully.
You have access to the following contexts:
192.168.104.11
demo1
workload-vsphere-tkg5
If the context you wish to use is not in this list, you may need to try
logging in again later, or contact your cluster administrator.
To change context, use `kubectl config use-context <workload name>`
-Found 4 kubernetes Workload Cluster VMs
-Found CAPI Machine Object in SC. VM Name = workload-vsphere-tkg5-control-plane-gq26b
-Found VM matching CAPI Machine Name in VC API. VM=workload-vsphere-tkg5-control-plane-gq26b.
-Found CAPI Machine Object in SC. VM Name = workload-vsphere-tkg5-default-nodepool-kph4q-64877fc9f4-85b58
-Could not find specified VM with VC API
-Found CAPI Machine Object in SC. VM Name = workload-vsphere-tkg5-default-nodepool-kph4q-64877fc9f4-9b8l2
-Could not find specified VM with VC API
-Found CAPI Machine Object in SC. VM Name = workload-vsphere-tkg5-default-nodepool-kph4q-64877fc9f4-ttn7s
-Could not find specified VM with VC API
STEP 2 - Stopping WCP Service on vCenter
-Press Enter to confirm/continue...
STEP 3 - Shutting Down all Supervisor Control Plane VMs
-Found Supervisor Control Plane VM SupervisorControlPlaneVM (3).
-VM SupervisorControlPlaneVM (3) is running on ESX host pacific-esxi-52.env1.lab.test
-ESX host pacific-esxi-52.env1.lab.test has Management IP 192.168.100.52
--Shutting down VM SupervisorControlPlaneVM (3) on host 192.168.100.52
/home/nverma/workspace/wcp-shutdown/wcp-shutdown.py:32: DeprecationWarning: ssl.PROTOCOL_TLSv1_2 is deprecated
context = ssl.SSLContext(ssl.PROTOCOL_TLSv1_2)
--Successfully logged in to VIM API
--Found SC Virtual Machine on ESX
--name : SupervisorControlPlaneVM (3)
--instance UUID : 500a4998-1cd2-8278-1743-4e103279c45f
--bios UUID : 420a82f3-6bbd-8472-4376-143930145b56
--path to VM : [vsanDatastore] a96b8562-d468-54a8-191d-00505686dede/SupervisorControlPlaneVM (3).vmx
--host name : pacific-esxi-52.env1.lab.test
--last booted timestamp : 2022-07-11 23:58:56+00:00
-Shutting dow VM SupervisorControlPlaneVM (3)
-Pausing for 75 seconds...
-Found Supervisor Control Plane VM SupervisorControlPlaneVM (2).
-VM SupervisorControlPlaneVM (2) is running on ESX host pacific-esxi-51.env1.lab.test
-ESX host pacific-esxi-51.env1.lab.test has Management IP 192.168.100.51
--Shutting down VM SupervisorControlPlaneVM (2) on host 192.168.100.51
--Successfully logged in to VIM API
--Found SC Virtual Machine on ESX
--name : SupervisorControlPlaneVM (2)
--instance UUID : 500a1e2c-ed13-b5bd-9cdb-6b00b80ac551
--bios UUID : 420a4f0e-2eb7-28a2-0ca8-f13c790a926d
--path to VM : [vsanDatastore] a96b8562-ac9f-3fda-5020-0050568663db/SupervisorControlPlaneVM (2).vmx
--host name : pacific-esxi-51.env1.lab.test
--last booted timestamp : 2022-07-12 00:00:08+00:00
-Shutting dow VM SupervisorControlPlaneVM (2)
-Pausing for 75 seconds...
-Found Supervisor Control Plane VM SupervisorControlPlaneVM (1).
-VM SupervisorControlPlaneVM (1) is running on ESX host pacific-esxi-53.env1.lab.test
-ESX host pacific-esxi-53.env1.lab.test has Management IP 192.168.100.53
--Shutting down VM SupervisorControlPlaneVM (1) on host 192.168.100.53
--Successfully logged in to VIM API
--Found SC Virtual Machine on ESX
--name : SupervisorControlPlaneVM (1)
--instance UUID : 500accbe-e45a-2a17-8d7c-54ce22e77d82
--bios UUID : 420aafd3-ba73-2454-cbba-1eefd435c892
--path to VM : [vsanDatastore] a96b8562-b6ac-d6f7-bf21-005056863b0f/SupervisorControlPlaneVM (1).vmx
--host name : pacific-esxi-53.env1.lab.test
--last booted timestamp : 2022-07-11 23:50:54+00:00
-Shutting dow VM SupervisorControlPlaneVM (1)
-Pausing for 75 seconds...
-Press Enter to confirm/continue...or Control-C or Control-X to stop program
STEP 4 - Shutting down all Guest Cluster VMs
-The following Workload Cluster VMs will be shutdown
workload-vsphere-tkg5-control-plane-gq26b
-Press Enter to confirm/continue...
--Shutting dow VM workload-vsphere-tkg5-control-plane-gq26b.
--Pausing for 45 seconds...
POST STEPS - Successfully Completed Script - Cleaning up REST Session to VC.
After your planned maintenance is completed in order to start vSphere with Tanzu you simply need to start the 'wcp' service on vCenter using either govc or the appliance User Interface https://<VC-IP>:5480/#/ui/services