VMware vSphere Kubernetes Services (VKS) Reviews & Product Details

The Service is seamlessly it bridges traditional VM management with modern containerized workload. Developers get self-service, native Kubernetes APIs to spin up clusters effortlessly, while sysadmins can manage pods directly inside vCenter alongside standard VMs using familiar governance teams, simplifying enterprise application modernization signficantly. Supports and onboarding are remarkably smooth. Futhermore, intergrated AI and intelligent automation optimize workload placement and resource utlization, makes enterprise cluster management truly efficient. Review collected by and hosted on G2.com.

The performance drawback of VKS is the heavey hypervisor tax and resouce overhead. Running Kubernetes on top of ESXi interduce CPU scheduling contention, particulary when deploying oversized worker nodes. This co-scheduling overhead can sevrely degrade pod throughput and latency. Additionally, control plane components consume massive amounts of resurces. You ultimately pay a noticeable performance penalty for that tight vSphere abstraction layer. Review collected by and hosted on G2.com.

The biggest win for us has been bringing container and VM operations together under one roof. Our infra team didn’t have to learn an entirely new toolchain—spinning up a Tanzu Kubernetes Cluster (control plane, worker nodes, the works) happens right inside vSphere Client, using the same namespace-based workflow we already rely on for everything else. We created a dedicated namespace ("primp-industries") and had a cluster up and running in minutes, not days.

What really sold the team, though, was the single-pane visibility. Node health, control plane status, CPU/memory allocation, storage policies—it’s all available in one dashboard instead of being split between a Kubernetes-specific tool and a separate vCenter view. With content library integration for our TKG cluster images and the built-in CLI tooling, day-to-day operations feel much less fragmented than they did in our old setup. Review collected by and hosted on G2.com.

Onboarding was pretty rough for anyone on the team without a Kubernetes background. Getting the supervisor cluster, the namespace structure, and storage policies configured correctly took real ramp-up time. A few of the configuration panels—especially the ones for setting per-namespace resource limits—feel less intuitive than they should. Also, when a node goes unhealthy, we often end up leaving the vSphere UI entirely to dig through logs elsewhere, which undercuts the “everything in one place” promise a bit. Post-Broadcom licensing costs are another area we’re watching closely as we think about scaling this up. Review collected by and hosted on G2.com.

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.

What I like most about VMware vSphere Kubernetes Services (VKS) is how cleanly it manages the entire cluster lifecycle without disrupting our existing infrastructure tooling. Because it’s tightly integrated through the Supervisor layer, we get native Cluster-API automation out of the box. Spinning up, upgrading, or deleting CNCF-conformant guest clusters now takes minutes instead of days.

The biggest operational time-saver for us is that day-2 tools like Cert Manager or ArgoCD can be deployed directly through a unified, operator-driven add-on system. On top of that, we no longer have to wait months for upstream Kubernetes minor-version releases the way we used to. Review collected by and hosted on G2.com.

What I dislike most about VMware vSphere Kubernetes Services (VKS) is the architectural friction that shows up right at the integration layer. On paper, the idea of running Kubernetes natively on top of ESXi sounds great, but in production it often feels like a mishmash of separate systems VKS, NSX, vCenter, and AVI each with its own expectations and knobs. Because you’re effectively managing overlapping control planes, you keep running into restrictive, “all-or-nothing” permission roadblocks, where even standard cluster admin roles can’t perform basic actions like listing Kubernetes nodes.

And when something goes out of sync between the vSphere Supervisor layer and the guest clusters, troubleshooting turns into an exhausting loop: logging into vCenter via root SSH, tracing custom Python scripts, and then hunting down API mismatches to figure out what broke and where. Review collected by and hosted on G2.com.

I find VMware vSphere Kubernetes Services (VKS) really valuable because it provides a straightforward path for organizations moving from traditional server setups to containerization without the cost or hassle of re-architecting everything. I like how we can run containerized applications alongside virtual machines without needing new hardware, which eliminates infrastructure silos and helps with on-demand scaling. It's easy to understand for those familiar with vCenter, reducing the learning curve since it's all under one console. I really value the vSphere Namespaces and Cloud Native Storage features because they allow our team to define multi-tenant security boundaries efficiently. The initial setup was super easy, kind of like deploying any other hypervisor. Review collected by and hosted on G2.com.

The licensing and Broadcom portfolio complexity is a bit of a problem. The new licensing structure requires getting the full VCF suite just to access the Kubernetes features, which is quite inconvenient. Instead of allowing us to purchase modular, targeted licenses for standalone Kubernetes orchestration, we're forced into comprehensive bundles with a minimum of 16 core CPU, which unnecessarily inflates the total cost of ownership. Review collected by and hosted on G2.com.

At Telus Digital we used VKS to move our IVR backend (Node.js with MySQL and Redis) from on-premise virtual servers into Kubernetes. I created the clusters myself, one per client, and kept their definitions as YAML files in a GitLab repository. What I liked most was how stable it was: our first client's cluster ran for a long time with very little maintenance. At one point we had to move that cluster to a new server, and because everything was defined in YAML, it was just a matter of deploying the cluster again in the new location. It also fit into the VMware environment we already had, so we didn't need a separate platform just for Kubernetes. Review collected by and hosted on G2.com.

The learning curve is steep, and I found the knowledge fades if you don't use it regularly. Ironically, because the clusters were so stable, we rarely touched their configuration. So when a change or upgrade was eventually needed, I had to spend time relearning the commands and how the pieces fit together before I could make the change confidently. Review collected by and hosted on G2.com.

What I like most about VKS is that it brings native Kubernetes support directly into the vSphere environment we already manage, so our team doesn’t have to context-switch between separate platforms to run containerized and VM-based workloads side by side. The UI/UX is a real strength: we can provision and monitor Kubernetes clusters right from vCenter using the same dashboard and permissions model we already rely on, which noticeably flattened the learning curve for our ops team.

On the integration side, it works smoothly with the rest of the VMware stack (vCenter, NSX for networking, and vSAN for persistent storage). That meant we didn’t have to stitch together a separate CNI or storage layer the way we would with a standalone Kubernetes distribution. Performance has also been reliable as we’ve scaled up cluster nodes, and since it runs on the same infrastructure as our existing VMs, we get consistent resource management and capacity planning across both container and VM workloads instead of treating them as separate silos. Review collected by and hosted on G2.com.

The biggest downside is that VKS still feels tightly coupled to the VMware ecosystem, so the UI/UX for cluster configuration can get complicated if you’re used to a simpler, cloud-native Kubernetes experience. There’s a real learning curve in translating standard kubectl/YAML workflows into the way vSphere expects things to be set up.

Integrations with tools outside the VMware stack—like external CI/CD pipelines or third-party observability platforms—also take more manual wiring than they would with a cloud-managed Kubernetes service, since a lot of the surrounding tooling assumes you’re running in AWS/GCP/Azure rather than on-prem vSphere. On the performance side, we’ve noticed that spinning up new clusters or scaling node pools can be slower than expected compared to public-cloud Kubernetes offerings, which can disrupt fast-iteration workflows.

Pricing and ROI are a real consideration as well. VKS effectively requires being fully invested in VMware licensing (vSphere, vSAN, NSX), so the total cost of ownership can end up higher than open-source Kubernetes if you’re not already committed to that stack. For support and onboarding, our team’s vSphere background helped, but getting support specifically for Kubernetes-related issues (versus general vSphere issues) sometimes meant navigating multiple support queues before reaching someone with the right expertise.

Finally, on AI/intelligence, the operational insights through Aria Operations are useful but still fairly basic for Kubernetes-specific troubleshooting. It doesn’t yet offer the kind of deep, container-aware anomaly detection you’d expect from dedicated Kubernetes observability tools. Review collected by and hosted on G2.com.

I really appreciate how VMware vSphere Kubernetes Services (VKS) integrates Kubernetes with our existing vSphere environment. It simplifies cluster deployment and lifecycle management, allowing us to deploy Kubernetes without setting up a separate infrastructure. I also like the centralized management experience and the efficiency of using existing infrastructure and resources. This makes it easier for our team to operate Kubernetes while maintaining consistency within our environment. Additionally, the streamlined process reduces operational effort and overhead, particularly compared to managing self-hosted Kubernetes. Review collected by and hosted on G2.com.

A few areas could be improved. The initial setup and configuration can still be somewhat complex, especially for teams that are new to Kubernetes. Troubleshooting can also require knowledge of both Kubernetes and the underlying VMware infrastructure. I’d also like to see more detailed documentation, clearer error messages, and simpler troubleshooting workflows. Improvements in automation, monitoring, and integration with third-party Kubernetes tools would make VKS easier to operate at scale. The main challenges during the initial setup were around configuration dependencies and making sure the underlying vSphere environment was properly prepared. Networking configuration and resource planning needed careful attention, and when issues arose during deployment, it was not always clear whether they were related to Kubernetes, vSphere, networking, or configuration. Better step-by-step guidance and clearer explanations of common deployment errors would help. Review collected by and hosted on G2.com.

I like how well VMware vSphere Kubernetes Services (VKS) integrates Kubernetes with our existing vSphere environment. It simplifies cluster provisioning and lifecycle management while still giving developers a standard Kubernetes experience. It's valuable because we can use the same underlying compute, networking, storage, and access control for Kubernetes instead of building and managing a separate platform. The biggest value for our team comes from cluster lifecycle management, infrastructure integration, and compatibility with standard Kubernetes tools. I also find the governance integration and centralized management beneficial, allowing the team to continue using standard Kubernetes and DevOps tooling. Review collected by and hosted on G2.com.

The main area I think that could be improved is troubleshooting and overall operational visibility. When an issue involves both Kubernetes and the underlying vSphere infrastructure, finding the root cause can require checking multiple layers, especially for networking, storage, or more related problems. I'd like to see a more unified troubleshooting dashboard that connects Kubernetes events and logs with the underlying vSphere compute network and storage information. For example, if a pod is stuck in a pending state, it would be helpful if VKS could immediately indicate whether the root cause is insufficient resources, storage issues, networking problems, or unhealthy nodes. Review collected by and hosted on G2.com.

The centralized management, built-in lifecycle capabilities, and consistent environment are especially useful for teams running both traditional VMs and containerized workloads. It reduces the operational overhead of maintaining Kubernetes and makes cluster deployment and management more straightforward. Review collected by and hosted on G2.com.

The biggest downside for me is that the initial setup and configuration can feel pretty complex, especially for teams that are new to both Kubernetes and the VMware ecosystem. Troubleshooting can be challenging as well, since it often requires knowledge across multiple layers—from vSphere networking and storage all the way up to Kubernetes itself. Review collected by and hosted on G2.com.