Velero Joins CNCF Sandbox: What the Broadcom Donation Means

Kubernetes does not ship with native cluster-level backup. That gap has made Velero — the backup, restore, and disaster recovery project originally built by Heptio and later maintained by Broadcom through the VMware acquisition — one of the most widely adopted tools in the Kubernetes ecosystem. At KubeCon + CloudNativeCon Europe 2026 in Amsterdam, Broadcom announced it was donating Velero to the CNCF Sandbox.

That’s a meaningful governance event for platform teams who depend on it.

What Velero Does

Velero operates at the Kubernetes API layer rather than at the control-plane datastore level. This means it captures cluster state — workloads, namespaces, persistent volume data — in a way that travels portably across Kubernetes distributions and cloud environments. A Velero backup taken from an EKS cluster can be restored to GKE. A cluster migrated from on-premises to a managed cloud service retains its backup posture. For disaster recovery, rollback workflows, and multi-cluster migration, Velero is doing work that has no equivalent in the default Kubernetes toolset.

Why the Donation Happened

Broadcom’s stated objectives were explicit: expand the contributor base and establish vendor-neutral governance. After Broadcom’s acquisition of VMware in 2023, open-source projects under the VMware umbrella faced predictable uncertainty from enterprise users. Moving Velero to the CNCF removes Broadcom’s commercial interests from the project’s roadmap decisions and places it under the same governance model as Kubernetes itself, Helm, Argo CD, and other foundational platform tools.

The CNCF CTO framed it directly: “By joining the CNCF Sandbox, Velero gains a vendor-neutral home to foster community collaboration and growth.” The Sandbox tier is the entry point for CNCF projects — it signals community interest and active development without the maturity guarantees of Incubating or Graduated projects. The expectation is that Velero moves up the maturity ladder as governance stabilizes and contribution velocity increases.

The announcement was paired with Broadcom’s VKS 3.6 (vSphere Kubernetes Service) release, which suggests Broadcom retains strong commercial interest in the Kubernetes ecosystem even as it relinquishes direct control over Velero specifically.

What Changes for Platform Teams

In practice, not much changes immediately. Velero continues to work the same way. What changes is the confidence model: organizations that hesitated to deepen their Velero dependency due to Broadcom’s single-vendor control now have a clearer path. CNCF governance means the project’s direction is influenced by a broader contributor base, not one company’s product roadmap. For procurement and compliance teams, CNCF Sandbox membership also simplifies vendor risk assessments — it’s a recognized governance standard in enterprise Kubernetes deployments.

The longer-term implication is contribution velocity. Broadcom’s internal team was the primary contributor. Under CNCF governance, teams at AWS, Google, Azure, and independent platform organizations have clearer incentive to contribute — their contributions won’t be filtered through a competitor’s product priorities. That dynamic has historically accelerated maturity for CNCF projects that start with strong existing user bases.

Source: The New Stack

Content created with AI assistance and reviewed for accuracy.