What I liked most was that VKS let us run Kubernetes workloads natively alongside our traditional VMs, without needing a separate management plane. We could provision namespaces directly from the vSphere Client, and bringing up a Tanzu Kubernetes Cluster—complete with its control plane and worker nodes—took only a few clicks in the same interface our infrastructure team already used every day. Having a single, consolidated dashboard to monitor cluster health, CPU and memory capacity, and storage policies significantly reduced the context-switching we used to do between separate Kubernetes and virtualization tools. The CLI tools link and the content library integration also helped make day-to-day cluster management smoother for our team. Review collected by and hosted on G2.com.

The initial setup—especially configuring the supervisor cluster, namespaces, and storage policies correctly—came with a fairly steep learning curve for team members without prior Kubernetes experience. A few configuration screens weren’t always intuitive, and troubleshooting unhealthy nodes sometimes meant digging through logs outside the vSphere UI rather than being able to resolve everything in one place. Licensing costs after the Broadcom acquisition were also a consideration for teams looking to evaluate and roll this out at scale. Review collected by and hosted on G2.com.