Broadcom Moves VM API to CNCF: What It Means for Kubernetes

The News

At KubeCon North America 2026, Broadcom announced that its VM API project has been accepted into the Cloud Native Computing Foundation (CNCF) Sandbox, placing virtual machine lifecycle management under vendor-neutral, community-driven stewardship. The VM API enables VMs to be provisioned and managed through Kubernetes APIs across heterogeneous infrastructure providers, treating them as first-class citizens alongside containers in a unified control plane. Broadcom also announced co-chairmanship of a new Workload Conformance Working Group within the Kubernetes community, and the validation of more than 20 new partner solutions for VMware vSphere Kubernetes Service (VKS).

Analyst Take

Why the CNCF Contribution Is Strategically Larger Than It Looks

On the surface, donating VM API to the CNCF looks like a routine open-source contribution. It isn’t. Broadcom is effectively making a standards-layer bet: if VM management in Kubernetes becomes governed by a community specification rather than a proprietary VMware API, every infrastructure vendor that wants to play in the Kubernetes ecosystem has an incentive to implement against that spec. That shifts the center of gravity for VM-plus-container workloads away from hypervisor-specific implementations and toward a common control plane, one that Broadcom, as a top-five long-term CNCF contributor and co-chair of the new Workload Conformance Working Group, is positioned to shape.

The timing connects directly to the AI workload dynamic the announcement highlights. According to the Linux Foundation’s 2026 Virtual Machines Report cited in the press release, VMs account for 53% of production applications, and 34% of organizations expanding their VM footprint point to AI and agentic workloads as a contributing factor. AI inference jobs with GPU passthrough, secure enclaves, and strict hardware isolation requirements do not map cleanly onto containers. Organizations that have already standardized on Kubernetes as their control plane now face an architectural gap: they want declarative, API-driven management of VMs through the same toolchain they use for pods. VM API is a direct answer to that gap.

The Vendor Lock-In Signal Worth Watching

The IDC quote embedded in the press release is the tell: “Conformance with open standards from the CNCF also helps mitigate vendor lock-in concerns as organizations decide how each workload should run.” For ITDMs evaluating VMware Cloud Foundation, vendor lock-in is a live concern, not an abstract one. According to ECI Research’s Google GovTech Survey, 52.5% of respondents said they “evaluate lock-in risk but prioritize functionality,” while an additional 24.9% said they “will only adopt open-source or highly portable tools.” That’s a combined three-quarters of the market actively weighing portability. By placing VM API in CNCF stewardship, Broadcom is directly addressing the most common adoption objection. Whether the community perceives this as genuine openness or as a strategic move to make Broadcom’s implementation the de facto reference is a separate question, and one worth monitoring as the Workload Conformance Working Group matures.

What VKS Partner Validation Means for Platform Engineering Teams

The 20-plus new validated partner solutions for VKS matter for a different reason than the CNCF contribution. Platform engineering teams running production Kubernetes clusters care about ecosystem depth, specifically whether the observability, security, storage, and application delivery tools they already rely on will integrate cleanly with their chosen runtime. Broadcom’s validated partner list now spans Datadog, Grafana Labs, Splunk by Cisco, CrowdStrike, Sysdig, Canonical Apache Spark, Akuity (the team behind Argo CD), and others. That coverage addresses the full operational stack, not just day-one provisioning. For developers, the practical implication is straightforward: fewer integration unknowns when adopting VKS in a brownfield environment.

The procurement and selection signal here connects to a clear finding from ECI Research’s Google GovTech Survey: 47.2% of respondents selected “Developer velocity and ease of integration” as the greatest weight in their final technical selection process (assuming baseline security and compliance are met). A runtime that ships with pre-validated integrations across observability, security, and data reduces the integration burden that otherwise falls on platform teams, which maps directly to what buyers say they’re optimizing for.

Looking Ahead

The Workload Conformance Working Group is the initiative to watch over the next 12–18 months. If Broadcom successfully builds multi-vendor participation in that working group, the resulting conformance standard could do for workload portability what the CNCF’s Certified Kubernetes Conformance Program did for platform portability: create a clear baseline that reduces buyer risk and accelerates adoption. Competitive pressure from Red Hat OpenShift Virtualization and the broader KubeVirt ecosystem means Broadcom cannot afford to let VM API sit in the sandbox without active community engagement, and the co-chair role signals it understands that.

For enterprise platform engineering teams, the practical decision point will arrive when the Workload Conformance standard reaches a stable specification, likely 2027 at the earliest. Until then, VKS’s value proposition rests on the ecosystem validation program and the unified control plane architecture. Organizations running heterogeneous infrastructure with a growing share of AI workloads should treat VM API’s CNCF acceptance as a signal to revisit their VM management strategy now, before AI infrastructure decisions lock them into architectural choices that are harder to unwind later.

Authors

  • Paul Nashawaty

    Paul Nashawaty, Practice Leader and Lead Principal Analyst, specializes in application modernization across build, release and operations. With a wealth of expertise in digital transformation initiatives spanning front-end and back-end systems, he also possesses comprehensive knowledge of the underlying infrastructure ecosystem crucial for supporting modernization endeavors. With over 25 years of experience, Paul has a proven track record in implementing effective go-to-market strategies, including the identification of new market channels, the growth and cultivation of partner ecosystems, and the successful execution of strategic plans resulting in positive business outcomes for his clients.

    View all posts
  • Samantha Weston

    With over 15 years of hands-on experience in operations roles across legal, financial, and technology sectors, Sam Weston brings deep expertise in the systems that power modern enterprises such as ERP, CRM, HCM, CX, and beyond. Her career has spanned the full spectrum of enterprise applications, from optimizing business processes and managing platforms to leading digital transformation initiatives.

    Sam has transitioned her expertise into the analyst arena, focusing on enterprise applications and the evolving role they play in business productivity and transformation. She provides independent insights that bridge technology capabilities with business outcomes, helping organizations and vendors alike navigate a changing enterprise software landscape.

    View all posts