Broadcom's VM API Enters CNCF Sandbox, Targeting Multi-Cloud Infrastructure Lock-In
Broadcom contributed its VM API project to the CNCF and is co-chairing a Kubernetes workload conformance group. Both target proprietary infrastructure APIs and fragmented certification across cloud providers.
Broadcom targets two multi-cloud friction points
Broadcom announced that its VM API project was accepted into the Cloud Native Computing Foundation Sandbox at KubeCon North America 2026. The project provides Kubernetes APIs for provisioning and managing virtual machines across heterogeneous infrastructure providers. Broadcom is also co-chairing a new Kubernetes Workload Conformance Working Group intended to establish common expectations for application behavior across Kubernetes distributions.
The dual move targets two major sources of multi-cloud lock-in: infrastructure APIs and workload certification. VM API competes indirectly with provider-specific approaches such as VMware vSphere APIs, AWS EC2 tooling, Azure Stack/AKS integrations, and Google Cloud's Kubernetes services. Its competitive significance is not immediate replacement—the CNCF Sandbox designation signals an early-stage project—but that it could give enterprises a more provider-neutral management layer for mixed VM and container estates.
The workload-conformance effort challenges the current model in which software vendors validate separately against Kubernetes distributions such as VMware Tanzu/VKS, Red Hat OpenShift, Amazon EKS, Microsoft AKS, and Google GKE. A shared conformance baseline could reduce certification work, although no performance or cost-reduction benchmark was disclosed.
In parallel, Broadcom validated more than 20 additional partner products for VMware vSphere Kubernetes Service, including offerings from Datadog, Grafana Labs, New Relic, Splunk, CrowdStrike, Sysdig, Tigera, Canonical, H2O AI Cloud, Traefik Labs, Dell, and Scality. The validations strengthen VMware's ecosystem position for buyers seeking supported observability, security, AI, application-delivery, and data-protection integrations.
What this means for infrastructure buyers
Enterprises standardizing on Kubernetes can evaluate whether VM API reduces dependence on proprietary VM-management interfaces, but should treat it as an emerging technology rather than a production-standard replacement. Platform teams may gain a common operational model for VMs and containers spanning on-premises infrastructure and multiple public clouds.
Procurement teams should not assume portability eliminates switching costs. Storage, networking, identity, observability, support contracts, and cloud-specific managed services remain major lock-in points. VM API addresses the control plane, not the data plane or the commercial relationships that create most multi-cloud friction.
This is a standards-and-ecosystem development, not yet a quantified cost-saving event. The immediate buying consequence is greater reason to test Kubernetes as a cross-environment abstraction layer, while delaying any assumption that VM API or workload conformance is mature enough to support wholesale cloud migration.
Canonical and Tigera offer multi-tenant Kubernetes reference architecture
Canonical and Tigera announced a collaboration combining Canonical's supported, CNCF-compliant Kubernetes distribution and Ubuntu Pro with Tigera's Calico networking, zero-trust security, and microsegmentation capabilities. The target environments include public cloud, on-premises virtual machines, and edge deployments.
The offering competes with integrated Kubernetes and hybrid-cloud stacks from Red Hat OpenShift, VMware Cloud Foundation/VKS, SUSE Rancher, and cloud-provider Kubernetes services such as EKS, AKS, and GKE. Calico also competes with Cilium and cloud-native network-security products from vendors including Isovalent and Palo Alto Networks.
The announcement provides no disclosed price, customer count, deployment scale, performance benchmark, or quantified security improvement. It gives buyers another supported reference architecture for multi-tenant Kubernetes where network segmentation and policy consistency matter across environments. It may be relevant to regulated enterprises that need Ubuntu support, Kubernetes compliance, and centralized network policy across cloud and edge locations.
Buyers should request hard data before treating the partnership as a reason to consolidate vendors: supported Kubernetes versions, policy portability, licensing costs, latency overhead, upgrade responsibilities, and independent benchmark results were not provided.
What to watch
The strongest near-term indicator is whether VM API progresses beyond the CNCF Sandbox and whether the Workload Conformance Working Group produces an implementable test suite. Until then, enterprise buyers should treat Broadcom's announcement as a signal of strategic direction and ecosystem formation—not as proof that workloads can move between AWS, Azure, Google Cloud, VMware, and on-premises environments without application, networking, storage, or operational changes.
The more than 20 validated VKS partner products represent a concrete step for buyers already committed to VMware infrastructure. For those evaluating whether Kubernetes can serve as a cross-cloud abstraction layer, VM API is worth tracking but not yet betting on.
Technology decisions, clearly explained.
Weekly analysis of the tools, platforms, and strategies that matter to B2B technology buyers. No fluff, no vendor spin.
