Watch on YouTube
Watch on Vimeo
VMware by Broadcom’s Jeremy Wolf, a lead product manager on the VMware vSphere Kubernetes Service (VKS) and Supervisor team, used this Tech Field Day session at KubeCon North America 2026 to show that vSphere is an advantage for running Kubernetes. Enterprises have spent 20 years running mission-critical, highly available applications on vSphere, and VKS lets them apply that same foundation to modern and AI workloads. Wolf walked through the three stages of running a Kubernetes platform. At day-zero, the Supervisor provides a Kubernetes control plane on the infrastructure, and vSphere Namespaces handle tenancy, role-based access control, network assignment, and storage quotas. During the build phase, Cluster API deploys clusters declaratively, and app teams request changes as variable overrides to a cluster class. For day-two operations, VKS clusters directly inherit vSphere HA, DRS, vMotion, and compute oversubscription features such as memory tiering. VI admins keep working in vCenter, owning hosts, capacity, storage, and networks, while platform engineers use familiar tools such as kubectl, Helm, Argo CD, and the VCF CLI.
Wolf described how two schedulers work together: DRS places VKS control plane and worker node VMs to avoid noisy neighbors, and the Kubernetes scheduler then places pods within those nodes, each with its own affinity and anti-affinity controls. When an admin puts an ESX host into maintenance mode, vMotion moves the worker node VM to another host without draining the node, rescheduling pods, or detaching persistent volume claims, so application teams never notice. Workloads pinned to a host through PCI passthrough devices such as GPUs or host-local datastores are the exception, and Broadcom is building a way for those workloads to request a warning so they can drain cleanly first. Unplanned host failures involve three recovery clocks: vSphere HA restarting the VM on another host, the Kubernetes node controller replacing an unreachable node, and pod eviction. In most customer environments, vSphere HA wins that race, and when it doesn’t, it usually comes down to insufficient spare capacity, so Wolf confirmed that customers should keep headroom in their clusters.
On storage, VM storage policies in vCenter are exposed to the Supervisor as Kubernetes storage classes, and the vSphere CSI driver works with Cloud Native Storage in vCenter to place each volume on a compliant datastore, which lets admins decommission a datastore with Storage vMotion while the pod’s storage class stays the same. On networking, the Supervisor supports VDS, NSX, and NSX VPC, and builds L4 load balancing into the platform from the start through the Foundation Load Balancer or NSX. For L7, customers can run Avi with its Kubernetes operator inside VKS clusters for enterprise tuning and visibility, or use an in-cluster controller such as Contour or Istio. Wolf framed Broadcom’s multi-cloud stance around portability: use VKS for on-premises Kubernetes, use EKS, AKS, or GKE in the public cloud, and manage both through GitOps, with Cluster API and the newly open-sourced VM API keeping clusters and VMs portable. He also clarified that Tanzu runs on top of VKS clusters within VCF, and closed by challenging viewers to deploy the Supervisor in a lab, run workloads on a VKS cluster, and put a host into maintenance mode to see the result for themselves.
Personnel: Jeremy Wolf
Thank you for being part of the Tech Field Day community! Our mailing list is a great way to stay up to date on our events and technical content, and we appreciate your signup.
We promise that we’ll never spam you, send ads, or sell your information. This list will only be used to communicate with our community about our events and content. And we’ll limit it to no more than one message per week.
Although we only need your email address, it would be nice if you provided a little more information to help us get to know you better!