WilliamLam.com

What's new in VMware Event Broker Appliance (VEBA) v0.7

by // 1 Comment

The VMware Event Broker Appliance (VEBA) team is excited to announce the availability of the highly anticipated VEBA v0.7 release! This is by far our largest release to date with the number of new features and functionality that has been added by our contributors. This has really been the result of closely collaborating and listening to the feedback provided by our VEBA users and community and helping drive our overall roadmap.

For those wishing to learn more about VEBA and the new v0.7 release, I did want to mention the following two VMworld 2021 sessions that may be of interests:

Without further ado, let's dive right into the new features!

[Read more...]

Updates to Nested ESXi Virtual Appliance for vSphere 7.0 Update 3

by // 16 Comments

vSphere 7.0 Update 3 officially GA'ed this morning and I am happy to share a quick that my Nested ESXi Virtual Appliance (OVA and Content Library) has also been updated to support the latest release. In addition, I have also published an update to the ESXi 7.0 Update 2a Virtual Appliance as there was an issue that prevented it from working with the latest VMware Cloud Foundation 4.x release.

Nested ESXi OVA:

Nested ESXi Content Library:

For prior ESXi versions, you can check out http://vmwa.re/nestedesxi

Single node Supervisor Control Plane VM for vSphere with Tanzu now possible in vSphere 7.0 Update 3

by // 8 Comments

Last year, when vSphere with Kubernetes (original name of what is now vSphere with Tanzu) was first released, I had shared a process on how to deploy a minimal setup including a detailed write-up for setting up vSphere with Tanzu on an Intel NUC with just 32GB of memory.

I am always looking for ways to simplify and ease the consumption of various VMware technologies within a homelab and I was pretty happy with the tweaks that I could make to reduce the amount of resources needed to run vSphere with Tanzu. Instead of needing to deploy three Supervisor Control Plane VMs, the modification to the vSphere with Tanzu configuration, allowed me to deploy just two Supervisor Control Plane VMs. It was unfortunate that deploying only a single Supervisor Control Plane VM at the time was not possible due to a known issue.

While deploying a pre-release of vSphere 7.0 Update 3 in one of my lab environments, I was going through the process of tweaking the vSphere with Tanzu configuration before enablement and I figure why not try the one node setting, in case it was fixed 🤷 I honestly was not expecting it to work since there was an internal bug that was filed awhile back and I had not seen the bug closed. To my complete surprise, vSphere with Tanzu enabled successfully and there was just a single Supervisor Control Plane VM!


It turns out that someone from Engineering must have fixed the issue and a single Supervisor Control Plane VM is now possible with the upcoming release of vSphere 7.0 Update 3! 🥳

UPDATE (07/02/24) - As of vSphere 8.0 Update 3, you no longer have the ability to configure a single Supervisor Control Plane VM using the minmaster and maxmasters parameters, which have also been removed from /etc/vmware/wcp/wcpsvc.yaml in favor of allowing users to control this configuration programmatically as part of enabling vSphere IaaS (formally known as vSphere with Tanzu). The updated vSphere IaaS API that allows users to specify number of Supervisor Control Plane VM will not be available until the next major vSphere release. While this regressed capability is unfortunate, it was also not an officially supported configuration and for users who wish to specify the number of Supervisor Control Plane VM using YAML method, you will need to use an earlier version of vSphere.

To change the settings, you will need to SSH to the VCSA and edit the following configuration file /etc/vmware/wcp/wcpsvc.yaml and search for minmasters and maxmasters and change the value from 3 to 1.

minmasters: 1
maxmasters: 1

For the changes to go into effect, you will need to restart the vSphere with Tanzu service which is listed as wcp by running the following command:

service-control --restart wcp

In addition, for homelab purposes, you may also want to change the controlplane_vm_disk_provisioning parameter, which defaults the Supervisor Control Plane VM to Thick provisioned rather than Thin, which many folks use in their labs.

controlplane_vm_disk_provisioning: "thin"