Recently, I found myself in the position of needing to shutdown a lab running PKS 1.2. A quick search revealed no documentation on this particular topic. Read on for details.
I suppose the bigger focus with Pivotal Container Service (PKS) is getting it up and running then maintaining it. There are plenty of blog articles and documentation on the many different aspects of those topics. The simple fact here though is that some people DO need to occasionally get an environment shutdown gracefully.
My case was this: my team’s Hardware Lab required a shutdown for a number of reasons related to the Physical Infrastructure maintenance being required. Many of the things running in the lab were vRealize related for our testing with Hybrid Cloud. The vRealize Suite is pretty well documented on proper shutdown sequence so no issue there. The challenge for me though was with PKS since it is something I’ve only recently begun working with. Of course my first instinct is to Google for official documentation, or better: Step-by-Step blog articles… however, this proved fruitless… I then checked Slack and asked an Expert… Fortunately, it’s not terribly complicated since we don’t have any workloads that are required to be running so I did the following:
- Deleted the 1 test Kubernetes cluster that had been deployed for integration testing with vRealize Automation 7.5
- Shutdown the VM running Bosh – It’s very important that this gets shutdown first since it will try to “fix” detected failures as the other components of PKS get shutdown
- Shutdown the VM running PKS
- Shutdown the VM running Harbor
- Shutdown NSX-T environment
This isn’t a highly detailed or technical article, but one that I hope helps others find a simple way to get their labs shutdown. Obviously Production environments would require far more detail that is beyond my current experience level.