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

How to shutdown and startup a Kubernetes cluster in VMware PKS (67656)

Last Updated: 4/9/2019Categories: How toTotal Views: 7386Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article describes how to safely shutdown and startup a VMware PKS cluster.
The BOSH deployment stop command does not follow the sequence needed for Kubernetes to shutdown cleanly. It is intended that the Worker VMs are shut down first and then the Master VMs are shut down.

Resolution

This procedure will allow you to successfully stop and start a Kubernetes cluster in VMware PKS environment.

Shutdown the Kubernetes Cluster:

Note the BOSH deployment name of your PKS cluster, it will be in the form of "service-instance_<cluster uuid>".

Get the BOSH VMs output for the PKS cluster deployment and confirm all services are running on each VM in the cluster.
bosh -d service-instance_xxxxxxxxxx is --ps

Note: If the cluster is not healthy it may cause issues after startup that are not related to this shutdown or startup procedure.

Stop the workers by executing the following command:
bosh -d service-instance_xxxxxxxxx stop worker

Stop the Masters by executing the following command:
bosh -d service-instance_xxxxxxxxxx stop master

Confirm the processes for all VMs are now showing unknown and the status of the VMs shows stopped.
bosh -d service-instance_xxxxxxxxxx is –ps

Startup the Kubernetes Cluster:

BOSH SSH to the first Master VM (master/0), sudo -i (switch to root user) and start the etcd service. Run monit summary to confirm the etcd service is now running and exit from the Master VM.
bosh -d service-instance_xxxxxxxxxx ssh master/0
sudo -i
monit start etcd
monit summary
exit
Note: If you have a single master K8S Cluster, power on the master node and then proceed with worker nodes.

Start the next Master VM using the BOSH start command. This will bring all services up on Master index 1 VM.
bosh -d service-instance_xxxxxxxxxxxx start master/1

At this stage you will have the etcd service running on 2 Master VMs which means etcd has quorum once again. Run BOSH start against all Masters in the Master instance group to bring up the remaining services.
bosh -d service-instance_xxxxxxxxxx start master

Confirm that all services for each master VM are now up and running.
bosh -d service-instance_xxxxxxxxxxx is –ps

Next start the worker VMs:
bosh -d service-instance_xxxxxxxxxxx start worker

The cluster should be back up and running now. Use BOSH is --ps to confirm all services are running for each VM.
bosh -d service-instance_xxxxxxxxxx is –ps

Confirm the componentstatus of Kubernetes shows all 3 etcd services are Healthy.
kubectl get componentstatus

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

Result 1 of 1

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