The News
Broadcom has announced a significant expansion of its Kubernetes portfolio under the VMware Cloud Foundation (VCF) umbrella, timed to coincide with KubeCon North America 2026 in Salt Lake City. The centerpiece of the announcement is the contribution of VM API to the Cloud Native Computing Foundation (CNCF) Sandbox, enabling virtual machines to be managed through Kubernetes-native declarative APIs across multiple infrastructure providers. Alongside the upstream contribution, Broadcom released VMware vSphere Kubernetes Service (VKS) 3.8, introducing automated chained upgrades, CISA/NSA/CIS-aligned policy bundles, native Tekton CI/CD pipelines, and External Secrets Operator integration, while expanding its validated partner ecosystem to include observability, security, storage, and AI/data vendors such as Datadog, Wiz, HashiCorp Vault, and H2O.ai.
Analyst Take
The VM API contribution is a strategic play, not just a community gift
Contributing VM API to the CNCF is the most consequential item in this announcement, even if it reads like a footnote next to the VKS 3.8 feature list. Broadcom is essentially proposing that the industry adopt a community-owned, provider-agnostic API surface for VM lifecycle management on Kubernetes. Today, organizations running mixed VM and container estates on Kubernetes are effectively locked into the virtualization vendor that controls that API. If VM API matures in the CNCF and earns broad adoption, Broadcom benefits in two ways: it gains goodwill and contributor influence in the upstream community, and it repositions VMware Cloud Foundation as the reference implementation of a standard rather than a proprietary island. The competitive implication is direct. Red Hat OpenShift Virtualization and other Kubernetes-native VM platforms will now need to engage with an emerging community standard they did not initiate.
What VKS 3.8 actually solves for platform engineers
The operational improvements in VKS 3.8 address real friction points that have frustrated platform teams for years. Automated Chained Upgrades is the clearest example: multi-version Kubernetes upgrades across large cluster fleets have historically required manual sequencing, dependency validation, and significant maintenance windows. Automating that chain with built-in dependency checking is the kind of unglamorous feature that earns genuine loyalty from infrastructure operators. Similarly, the Policy Bundles with OPA Gatekeeper deliver pre-configured compliance guardrails aligned to CISA, NSA, and CIS benchmarks, a meaningful reduction in the manual security work that precedes any audit. According to ECI Research’s Google GovTech Survey, 48.5% of respondents cited “Enforcing standardized security and compliance guardrails automatically” as the primary goal driving their organization toward an Internal Developer Platform approach. VKS 3.8 is directly answering that demand. The native External Secrets Operator integration also deserves attention: secrets sprawl across AWS Secrets Manager, Azure Key Vault, and HashiCorp Vault is one of the most common Zero Trust failure points in multi-cloud Kubernetes deployments, and centralizing that synchronization natively removes a category of manual credential management that has been a persistent source of security risk.
Developer experience is finally getting a line item
The inclusion of Tekton for native CI/CD and Headlamp for cluster inspection signals that Broadcom is no longer treating developer tooling as an afterthought in what has historically been an infrastructure-first product line. The OpenTelemetry integration with Datadog, Splunk, and New Relic is particularly well-timed. ECI Research’s Google GovTech Survey found that 47.2% of respondents selected “Developer velocity and ease of integration” as the factor carrying the greatest weight in their final technical selection process, assuming baseline security requirements are met. That is a striking number, and it reframes the competitive conversation: feature completeness and performance matter, but if platform teams cannot get developers productive quickly, the platform loses at the point of adoption. Broadcom appears to have absorbed that lesson. The NFS-Client for dynamic persistent volume creation across existing NetApp and Dell NAS hardware is also worth noting for enterprise accounts. It eliminates a common friction point where storage teams and platform teams are negotiating over vendor-specific CSI drivers, and it gives legacy workloads a path onto Kubernetes without requiring a storage refresh.
The ecosystem expansion signals a shift in go-to-market posture
The validated partner list, spanning Wiz, Dynatrace, H2O.ai, Akuity, and HPE Alletra among others, reflects a deliberate move away from the closed-stack model that defined early VCF positioning. Broadcom is communicating to enterprise buyers that VCF is an integration platform, not a replacement for the toolchain they already operate. That message matters because ECI Research’s Google GovTech Survey found that 52.5% of respondents described their vendor lock-in posture as “Moderate concern (We evaluate lock-in risk but prioritize functionality).” An additional 24.9% characterized their concern as paralyzing, willing to adopt only open-source or highly portable tools. Together, those numbers mean that the majority of enterprise platform buyers are actively factoring portability and ecosystem openness into procurement decisions. Broadcom’s partner validation program aims to directly address that concern.
Looking Ahead
The VM API CNCF contribution will take 12–18 months to reveal its true strategic value. If the project attracts contributions from major cloud providers and competing virtualization vendors, it becomes a genuine industry standard and Broadcom earns the credibility of having initiated it. Watch for whether AWS, Google Cloud, or Microsoft engage with the project in the first two sandbox governance cycles. Their participation could be the clearest signal of whether VM API becomes infrastructure-neutral or remains effectively VMware-adjacent.
For enterprise platform teams evaluating VCF refresh cycles in 2026–2027, the VKS 3.8 release makes the upgrade case materially stronger than it was twelve months ago. Automated Chained Upgrades, OPA-backed policy bundles, and native secrets synchronization collectively reduce the operational overhead that has caused many organizations to defer Kubernetes version currency. Broadcom’s 24-month extended lifecycle policy gives cautious buyers room to plan. The more interesting question over the next two to three years is whether the developer experience investments, Tekton, Headlamp, OpenTelemetry, accelerate VCF adoption in application development teams directly, rather than requiring a platform engineering team to serve as an internal sales force between the infrastructure and the developers who depend on it.
Stay Ahead of Application Development Trends
Get weekly analyst insights, research notes, event coverage, and AppDevANGLE updates delivered directly to your inbox.
Subscribe for Weekly Insights
Join technology leaders, practitioners, and GTM teams following the trends shaping modern software delivery.
Looking for deeper research access?
Explore ECI Research reports, survey insights, and market analysis through the ECI Research Portal.
