Broadcom Takes VM API to CNCF Sandbox and Opens a Workload Conformance Effort
- Harold Fritts
- 945 views
Broadcom's VM API enters the CNCF Sandbox, its new Workload Conformance group targets app-level portability, and 20+ partners are validated on VKS.

Broadcom's three Kubernetes announcements at KubeCon North America 2026 add up to one argument: virtual machines belong in the Kubernetes control plane, not beside it. Of the three, the VM API move into the CNCF Sandbox matters most, because it could change how other infrastructure vendors build VM support. The workload conformance group is still a blank page. The partner validations are the part you can act on this quarter.

What VM API Actually Changes
VM API lets you provision and manage virtual machines through Kubernetes APIs, across several infrastructure providers at once. A VM becomes a first-class Kubernetes resource, sitting next to containers under the same declarative model. That's the pitch, and it's a clear one.
The project grows out of Broadcom's VM Operator, which brought Kubernetes-native VM management to the vSphere side of VMware Cloud Foundation. It borrows its structure from Cluster API, the community project that abstracted cluster lifecycle across providers. That lineage is worth noting. Cluster API proved that a provider-neutral interface could work for cluster lifecycle, and VM API is an attempt to repeat the trick for virtual machines.
Moving the project under CNCF stewardship is meant to give other infrastructure providers a common API and operating model to implement. Workload consistency is supposed to come from conformance rather than from any one vendor's implementation. If that works, a provider that isn't Broadcom can offer the same VM resource model to its users. If it doesn't, VM API stays a vSphere-centric tool with an open-source label.
Broadcom's justification leans on the Linux Foundation's 2026 Virtual Machines Report, which surveyed 492 practitioners. Per the figures Broadcom cites, VMs still account for 53% of production applications, most organizations expect that share to hold, and 34% of organizations growing their VM footprint point to AI and agentic workloads as the reason. Broadcom argues that advanced AI workloads need the hardware isolation VMs provide, along with the agility of containers, and that VM API is how you run both under one Kubernetes control plane.
Dilpreet Bindra, senior director of engineering in Broadcom's VMware Cloud Foundation Division, put the goal this way: "By contributing the VM API project to CNCF, we are bringing that enterprise-grade reliability to the Kubernetes community." Broadcom also says it is among the top five long-term contributors to CNCF projects. That's a vendor claim, and you can check it against CNCF contributor data yourself.
A Workload Conformance Gap

Existing CNCF programs certify that a platform exposes the standard Kubernetes APIs, behaves correctly for core container orchestration, and can run AI and machine learning workloads portably. What's missing is anything equivalent for the workloads themselves. An independent software vendor that wants to sell into several Kubernetes distributions has to certify against each one separately.
The new Workload Conformance Working Group, which Broadcom co-chairs, aims to define a shared, verifiable standard for how workloads behave on any conformant Kubernetes environment. The pitch is that an ISV validates once and deploys everywhere. Broadcom notes that VMware helped pioneer Sonobuoy, the diagnostic engine behind the CNCF's Certified Kubernetes Conformance Program, so the company has a track record in this exact area.
Be realistic about timing, though. The group is newly formed and hasn't published a standard or a timeline. Right now it's a charter and a direction. Anyone planning vendor evaluations around it should treat it as a 2027-or-later consideration until it produces something testable.
Matthew Flug, research manager for Intelligent Application Modernization and Deployment Platforms at IDC, framed the stakes for buyers. He said the priority for organizations running both VMs and containers "is applying consistent governance and policy enforcement across both," and added that "conformance with open standards from the CNCF also helps mitigate vendor lock-in concerns as organizations decide how each workload should run."
Who's Validated on VKS
VKS is the CNCF-certified Kubernetes runtime built into VMware Cloud Foundation. It runs directly on the hypervisor, so VMs, containers, and AI workloads share the same clusters and one control plane. Broadcom says this removes the separate infrastructure layer a standalone Kubernetes distribution typically requires. Whether that saving holds up depends on your own sizing, but the architectural argument is clear.
The validated partner list is the practical part. Broadcom groups the new validations into six areas, joining an existing catalog that already includes names such as Cribl, Palo Alto Networks, F5, NetApp, Veeam, NVIDIA, and Redis:
- Observability: Cisco Splunk, Datadog, Dynatrace, Grafana Labs, and New Relic.
- Security and secrets management: CrowdStrike Falcon Platform, HashiCorp Vault, Sysdig Secure, Tigera Lynx, and Wiz.
- Networking, ingress, and service mesh: NetScaler ADC (Citrix), Solo.io (agentgateway, kagent, and Solo Enterprise for Istio), and Traefik Labs.
- Data protection, backup, and storage: Commvault, Dell Technologies PowerProtect Data Manager, HPE Alletra, and Scality RING.
- AI, machine learning, and analytics: Charmed Apache Spark from Canonical, H2O AI Cloud, and SAS Viya.
- Application delivery, databases, and developer platforms: Akuity Argo CD Enterprise and Kargo, KubeDB by AppsCode, Coherent Spark, and Siemens Mendix.
Broadcom's logic for the list is operational. Platform teams choose from a pre-validated catalog and keep the tools they already run as they move from day-one provisioning to day-two operations on VKS. The workload conformance group is meant to make that catalog grow without each vendor re-certifying for every platform. If you're already running any of these tools, the validation reduces the number of compatibility questions you need to answer before a VKS deployment.
Varun Verma, GVP of Engineering at New Relic, said, "Enterprises running critical workloads on VKS can't afford blind spots. With New Relic now validated on VKS, teams get unified cluster observability, find root causes faster, and tie operational performance directly to business impact."
Broadcom also named Notruf Niederösterreich, which runs a 24×7 operations center with a small IT team, as a VKS customer. Alexander Hopfgartner, Chief Technology Officer at Notruf Niederösterreich, said, "VMware vSphere Kubernetes (VKS) Service lets us spin up encapsulated environments and scale horizontally within hours of a major incident, without being locked into specific hardware. That flexibility is critical when our systems have to stay available." That's a customer quote supplied by Broadcom, so treat it as a reference point rather than independent performance data.
Broadcom also pointed to Velero 1.19, which adds block-level data movement; the Container Object Storage Interface, which is moving toward beta with a vSphere COSI driver; and Agent Substrate, a CNCF Sandbox initiative for running agents. If you run backup or object storage on VKS, those three items deserve a look before your next planning cycle.