<-- Back to All News

The CNCF Dividend: Broadcom Donates Velero to the Community

Publish Date: May 1, 2026

Executive Overview

In a strategic move that fundamentally reshapes the Kubernetes data protection landscape, Broadcom has officially donated Velero—the industry-standard open-source tool for Kubernetes backup and disaster recovery—to the Cloud Native Computing Foundation (CNCF). This transition occurs against a backdrop of intensifying demand for sovereign cloud capabilities and “Private AI” workloads that require robust, vendor-neutral recovery paths. By moving Velero to community governance, Broadcom is not merely offloading a project; it is fostering a “trust layer” for the entire VMware Cloud Foundation (VCF) ecosystem. This analysis explores how this shift from a proprietary-led model to a community-led one actually strengthens the VCF value proposition by ensuring that Kubernetes data mobility remains a standard, not a siloed feature.

Features

The latest technical version of Velero (v1.16) released alongside this donation introduces several key features that integrate deeply with the VCF 9.0 stack while maintaining open standards.

  • CRD-Native Backup Logic: Unlike legacy hypervisor-based snapshots, Velero operates at the Kubernetes API layer, capturing the “soul” of the application—its Custom Resource Definitions (CRDs), secrets, and configurations—independently of the underlying storage.
  • Enhanced etcd Diagnosis and Recovery: Integrated with the new etcd-diagnosis and etcd-recovery tools, Velero now provides automated paths to repair the Kubernetes control plane when the underlying key-value store becomes corrupted or desynchronized.
  • Multi-Cloud Mobility Hooks: A standardized set of migration APIs that allow workloads to be moved seamlessly between VKS (vSphere Kubernetes Service) and public cloud providers like AWS or Google Cloud without reformatting data structures.
  • CSI Snapshot Integration: Full support for the Container Storage Interface (CSI), allowing VCF 9.0 users to trigger high-performance vSAN snapshots directly from within the Kubernetes command line.
  • Sovereign-Ready Metadata Masking: New filters that allow organizations to strip PII (Personally Identifiable Information) from cluster metadata before it is backed up to off-site object storage, a critical requirement for GDPR and sovereign compliance.

Benefits

The donation of Velero and its continued integration into VCF 9.0 provides a “Resilience Dividend” that balances open-source flexibility with enterprise-grade support.

The primary benefit is Elimination of Lock-in Anxiety. Organizations can build their cloud-native strategies on VKS knowing that their backup format is a global standard, not a proprietary VMware secret. This leads to Accelerated Disaster Recovery; because Velero understands application topology, it can restore a complex microservices application across different VCF regions faster than a manual “re-deploy from scratch” ever could. Furthermore, Ecosystem Synergy is significantly enhanced, as third-party storage vendors are now more likely to contribute drivers to an independent CNCF project, thereby increasing the hardware compatibility list for VCF users.

Use Cases

  • Private AI Model Protection: Backing up the training state and vector database configurations for local LLMs, ensuring that a hardware failure doesn’t result in the loss of weeks of compute-intensive training.
  • Cross-Cloud Migration: Moving production workloads from an aging public cloud instance to a sovereign VCF 9.0 private cloud for better cost control and data residency compliance.
  • CI/CD Pipeline Rollbacks: Integrating Velero into the developer workflow to provide “automatic save points” before major application deployments, allowing for instant recovery if a new code push breaks the cluster.

Alternatives

  • Kasten by Veeam (K10): A highly polished, commercial alternative that offers deep integration with VCF and a more robust user interface. While Kasten provides superior ease of use for the “enterprise admin,” it carries a significant licensing cost compared to the open-source Velero.
  • TrilioVault for Kubernetes: Another strong commercial competitor focusing on multi-cloud data management. Trilio excels in complex OpenStack/Kubernetes hybrid environments but may offer more features than a “VCF-first” organization actually requires.
  • Native Storage-Level Replication: Relying on vSAN or array-level replication. While extremely fast for data, it is “application blind”; it copies the bits but often fails to capture the Kubernetes metadata required to actually run the application once it is restored.
  • Manual “GitOps” Recovery: Attempting to rebuild the environment from Git repositories and Helm charts. This is the ultimate “clean” recovery, but it is often too slow for production environments because it does not capture the “state” (the actual data in the databases) that has accumulated since the last commit.

Alternative Perspective

While the donation of Velero is framed as a community win, we must apply critical thinking to the “Strategic Abandonment” Theory. Is Broadcom truly fostering community growth, or is it reducing its internal R&D burden for a tool that has become a commodity? There is a risk that without the primary funding of a single large vendor, Velero’s development could fragment or slow down, leaving VCF users with a “stagnant standard.” Furthermore, we must question the “Complexity Paradox”—Velero is notoriously difficult to configure compared to commercial tools. By making it the “standard” for VCF, is Broadcom inadvertently forcing infrastructure teams to become “Velero engineers” just to maintain basic data protection? Finally, we must ask if “Universal Portability” is actually a myth; even with Velero, the differences in underlying networking (NSX vs. VPC) often make true “cross-cloud” restores a manual, error-prone nightmare.

Final Thoughts

The move to the CNCF is a masterstroke of “coopetition.” By relinquishing control of Velero, Broadcom has made it the “Linux of Kubernetes Backup.” For the VCF 9.0 customer, this means that their private cloud is now more open, more resilient, and more integrated into the global cloud-native ecosystem than ever before. The future of data management is not about who “owns” the code, but who “orchestrates” the outcome.

Source URL: https://blogs.vmware.com/cloud-foundation/2026/05/01/broadcom-donates-velero-to-cncf/ (and related technical disclosures)