Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Shutdown and Startup order for VMware PKS environment (67657)

Last Updated: 9/1/2023Categories: InformationalTotal Views: 5014Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

This article contains the information about Shutdown and Startup order for VMware PKS environment in case of any datacenter maintenance/Outages.

Resolution

In case of any datacenter maintenacne/outages, please follow the below order for shutting down / starting up the VMware PKS environment.

VMware PKS environment shutdown order:

Disable BOSH Resurrection: If you have the Enable VM Resurrector Plugin checkbox  selected in the BOSH Director tile > Director Config pane, you must turn BOSH resurrection off before restarting PKS, to prevent BOSH from recreating VMs. To do this, run the command bosh update-resurrection off

Applications/Pods: Stop all the apps/pods running on the K8S Clusters.

K8S Clusters:

Stop all the K8S nodes in each cluster by following Shutdown the VMware PKS Cluster section in the VMware KB article, How to shutdown and startup a VMware PKS Cluster.
Note: all processes on K8s nodes will be stopped. And BOSH will mark them as stopped so when the VM is powered on, the process won't start automatically.

Shutdown all the K8S node VMs from the vCenter.

Note: To shut down a virtual machine, right click the virtual machine in the VMware Host Client inventory, select Guest OS from the pop-up menu, and select Shut down. Follow the same to shutdown other virtual machines as well.

PKS Control Plane:

Stop the PKS API vm by using Bosh:
bosh -d pivotal-container-service-xxx stop

Shutdown the PKS API VM from the vCenter.

Harbor:

Stop the Harbor VM by using Bosh:
bosh -d harbor-container-registry-xxx stop

Shutdown the Harbor VM from the vCenter.

Bosh: Shutdown the Bosh VM from the vCenter.

Ops Manager: Shutdown the Ops Manager from the vCenter.

NSX-T: Shutdown the below NSX-T related VMs from the vCenter.

NSX-T Manager.

NSX-T Controllers.

NSX-T Edge nodes

vCenter: Shutdown the vCenter, for more information on how to shutdown the vCenter, see Reboot or Shut Down the vCenter Server Appliance section in the VMware Documentation.

ESXi Hosts: Put the ESXi’s in maintenance mode and then power them off (using iLO or other console methods)

VMware PKS environment Startup order:

ESXi hosts: Power on all the ESXi hosts (using iLO or other console methods).

vCenter: Connect to web interface of the ESXi hosting vCenter vm and power on the vm.

NSX-T: Power on all the NSX-T related VMs from the vCenter.

NSX-T Manager

NSX-T Controllers

NSX-T edge nodes

Ops Manager: Power on the Ops Manager from the vCenter.

Bosh:

Power on the Bosh VM from the vCenter.

If you are unable to connect to Bosh after powering on, see Unable to connect to Bosh client with an error "Requesting token via client credentials grant: UAA responded with non-successful status code '503' response 'FAILURE'" (67441)

At this point in time, BOSH won’t try to resurrect any VMs because BOSH knows all the VMs under its control were BOSH stopped.

PKS Control Plane VM:

Power on the PKS API VM from the vCenter.

If you are unable to connect to PKS VM after powering on, see PKS login fails with "Error: Unable to send a request to API: Head https://pks-api_FQDN:9021/v1/clusters: dial tcp pks-api-IP:9021: connect: connection refused" (65138).

Harbor:

Power on the Harbor VM from the vCenter.

Verify the Harbor status using Bosh and start services if required.

K8S Cluster nodes:

Start the each K8S cluster by following the Startup the VMware PKS Cluster section in VMware KB article, How to shutdown and startup a VMware PKS Cluster.

Applications/Pods : Start all the applications/pods as required.

Re-enable BOSH Resurrection :  Turn BOSH resurrection back on by running the command bosh update-resurrection on.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
「ホストは VMware vSphere Update Manager のパッチ ストアからファイルをダウンロードできません。ネットワーク接続およびファイアウォールの設定を確認してください。詳細は esxupdate のログを確認してください。(Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and (67705)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant