Under vSphere 8 you have two possible ‘quests’ when it comes to creating a vSphere Supervisor:
In this post, I would like to discuss the scenario with ‘NSX’, more specifically NSX with AVI as a load balancer, as this is possible since NSX 4.1.1.
Continue reading
With the release of vSphere 8U3, vSphere with Tanzu was not only renamed (multiple times) but also a step was taken to “decouple” TKGs from the vCenter version.
Until then, TKGs and vSphere with Tanzu were considered a single entity and thus synonymous with each other.
One disadvantage of this was that the available Kubernetes versions for the Tanzu Kubernetes clusters (i.e., the “child” clusters of the Supervisor Cluster) depended on the version of the vCenter Server.
If you wanted to use a current k8s release, the first step was inevitably to update the vCenter.
Since vSphere 8U3, in addition to the IaaS Control Plane vSphere Kubernetes Service, which provides the Supervisor, there is now also a TKGs Service responsible for the Tanzu Kubernetes Clusters (TKC). Since this can be updated independently, it allows quicker and easier access to current k8s releases 🥳🥳🥳
In the following, I’ll briefly show how to update this crazy thing .
Continue reading
The vSphere Lifecycle Manager has been accompanying us since vSphere 7, which not only allows us to equip hosts with the latest ESXi and vendor add-ons, but also to update hardware to be VSAN-compliant and equip it with fresh firmware.
Hardware manufacturers such as HPE, Dell, Lenovo, Fujitsu, etc. have continuously improved their support and expanded their Hardware Support Managers.
For administrators, it’s definitely worth using these tools. The manual firmware update process becomes as simple as a host update.
Here, we’ll discuss how to configure and use the Hardware Support Manager, specifically the HPE OneView for VMware vCenter, which we’ll refer to as OV4VC from now on.
Continue readingA few days back i had the challenge to convert a vSphere 7.0 U3 Cluster (which was still managed in Lifecylce Manager with Baselines –> which are finally going away after vSphere 8, btw., so it’s time to migrate, folks!) to a Single Image.
I’m not going into details about vSphere Lifecycle Manager with Single Image and/or Baselines here, there’s lot’s of other stuff to read about that on the internet.
The challenge here was that the vCenter had no connection to the internet, so all the benefits like giving me a long list of ESXi releases and Vendor Add-Ons was not the case, and I couldn’t find any advice in the documentation on how to do it “offline” and seperated from the World Wide Web.
So, let me show you how I did it.
Continue reading
Recently I had more to do with vSphere Replication and Site Recovery Manager (more specifically with versions 8.6) and would like to share my experiences with Traffic Separation for vSphere Replication with you.
Traffic separation is the possibility of splitting network traffic between different networks/port groups/VLANs and thereby possibly achieving an increase in security and performance.