WilliamLam.com

How to programmatically retrieve vCenter Server Patch & Update History?

by // 3 Comments

After upgrading my homelab to the latest vSphere 7.0 Update 3 release, I was just looking at the "History" tab within the Virtual Machine Management Interface (VAMI), which gives you a historical view of all the patches and updates that have been applied to your vCenter Server since its initial deployment. I am not exactly sure when this was feature was introduced, but it can definitely be useful for both auditing but also debugging/troubleshooting purposes.

Of course, I was curious about this information and wanted to see if I could retrieve it using something like PowerCLI. However when I started to look for the API, I realized that there may not be a public API for this ... but that did not stopped me and taking a look at Chrome Developer, I quickly saw the endpoint which was /rest/appliance/update/history and I was able to figure out a workaround giving the same data.

Below are two examples on accessing this data using either PowerShell or cURL

[Read more...]

Quick Tip - How to disable the vCenter Server Update Notification banner?

by // 4 Comments

I received this question on Twitter from Andreas asking the following:

When a new vCenter Server update is available, a notification banner is automatically displayed in the vSphere UI. This functionality was introduced as part of vSphere 7.0 and part of the new vSphere Lifecycle Manager (vLCM) capability. This is a very useful feature since administrators spend most of their time in the vSphere UI and when new update was available, it would only be displayed in the VAMI UI, which most folks were not logging into on a regular basis.


Today, the update notification banner is always displayed and there is no way to temporarily disable it. This can be annoying if you do not intend to update your vCenter Server immediately and I assume this is why Andreas was asking about either postponing or disabling the notification all together.

Currently, the only way I am aware of for disabling this notification is to actually disable the vCenter Server Life-Cycle Manager Remote Plugin itself. You can do this by navigating to Administration->Solutions->Client Plugins and then selecting "vCenter Server Life-cycle Manager" and click on the Disable button. You can refresh the webpage or logout and you should no longer see the notification banner.

Disclaimer: By disabling the vCLM plugin, you are disabling more than just the banner but all vCenter vLCM functionality including Interop and Update Planner capabilities. If these are things you require, do not disable the plugin.


I can certainly see a nice feature enhancement in the future where vLCM notifications can be postponed or deferred to a later date. I will share this blog post and feedback with the vLCM PM for consideration.

Tanzu Kubernetes Grid (TKG) Demo Appliance 1.2.0

by // Leave a Comment

Happy to share that the Tanzu Kubernetes Grid (TKG) Demo Appliance Fling has been updated to support the latest TKG 1.2.0 release which just came out a couple of weeks ago. The TKG Workshop Guide has been updated to reflect all new TKG 1.2 changes along with an updated vSphere Content Library containing all the OVA required to get started. As mentioned in the workshop guide, you can use either a VMware Cloud on AWS SDDC (1-Node) or a vSphere 6.7 Update 3/vSphere 7.0+ environment.

The most notable change with this version is actually within TKG itself which now uses kube-vip to replace the functionality that the HAProxy VM used to provide. What this means when deploying either a TKG Management or Workload Cluster is that you will need to specify an IP Address which will be used for the Virtual IP endpoint of the K8s Cluster as shown in the screenshot below.

tkg init -i vsphere -p dev --name tkg-mgmt --vsphere-controlplane-endpoint-ip 192.168.2.10


Using the TKG Demo Appliance, you can deploy both v1.19.1 and v1.18.8 K8s Clusters. To exercise a TKG Cluster upgrade workflow, you just have to run these three simple commands:

export VSPHERE_TEMPLATE=photon-3-kube-v1.18.8_vmware.1
tkg create cluster tkg-cluster-01 --plan=dev --kubernetes-version=v1.18.8+vmware.1 --vsphere-controlplane-endpoint-ip 192.168.2.11
tkg upgrade cluster tkg-cluster-01


There has been a lot of demand for TKG on VMware Cloud on AWS, so that is where I have spent the bulk of my testing not to mention where it was originally developed. You can also deploy the TKG Demo Appliance in an on-premises vSphere environment running 6.7 Update 3 or newer.

[Read more...]