In part 3, we will be creating a namespace and deploying a Tanzu Kubernetes Cluster.Continue reading “Implementing Tanzu in vSphere 7U1 Part 3: Creating Namespace and Tanzu Kubernetes Cluster”
I’ve been working on getting VMware Tanzu Kubernetes Grid deployed in my homelab for a bit now. While I have been able to successfully deploy the workspace management and supervisor cluster VMs, I have noticed very excessive disk I/O from those VMs.Continue reading “VMware Tanzu In My Homelab: Excessive Disk I/O”
In this post, we will walk through enabling and configuring vSphere’s Workload Management for the Tanzu Kubernetes Grid.Continue reading “Implementing Tanzu in vSphere 7U1 Part 2: Enabling Workload Management”
Finally got around to upgrading my vCenter 6.7 deployment to 7U1. I did run in to a couple snags; one with a solution, one I am still trying to figure out.
A while back, I was noticing some strange behaviors with some parts of the vSphere web client. Primarily, it was related to vSAN details.
The intention is to deploy a pair of high-availability pfSense VMs to handle the homelab routing along with configuring OSPF to take care of route propagation to my primary router. I don’t want to deal with static routes for a bunch of VLANs, or at least any that need outbound access, and my EdgeRouter supports OSPF.
Using VMware vSphere in a homelab, we don’t necessarily care for some of the health checks. Intel NUC are not on the HCL so you will get warnings; despite the hardware working without issue.
Replacing vCenter’s self-signed certificate is not that difficult, and there are some steps that can make it a little bit easier.