{"id":3822,"date":"2026-05-02T09:30:13","date_gmt":"2026-05-02T09:30:13","guid":{"rendered":"https:\/\/cloudobjectivity.co.uk\/?p=3822"},"modified":"2026-05-02T09:30:37","modified_gmt":"2026-05-02T09:30:37","slug":"the-cncf-dividend-broadcom-donates-velero-to-the-community","status":"publish","type":"post","link":"https:\/\/cloudobjectivity.co.uk\/index.php\/2026\/05\/02\/the-cncf-dividend-broadcom-donates-velero-to-the-community\/","title":{"rendered":"The CNCF Dividend: Broadcom Donates Velero to the Community"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"3822\" class=\"elementor elementor-3822\" data-elementor-post-type=\"post\">\n\t\t\t\t<div class=\"elementor-element elementor-element-5a87e807 e-flex e-con-boxed e-con e-parent\" data-id=\"5a87e807\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-3e48fd48 elementor-widget elementor-widget-text-editor\" data-id=\"3e48fd48\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t\t\t\t\t\t\n<p><\/p>\n\n\n\n<p><strong>Publish Date:<\/strong> May 1, 2026<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Executive Overview<\/h3>\n\n\n\n<p id=\"p-rc_89d88292695badd4-47\">In a strategic move that fundamentally reshapes the Kubernetes data protection landscape, Broadcom has officially donated Velero\u2014the industry-standard open-source tool for Kubernetes backup and disaster recovery\u2014to the Cloud Native Computing Foundation (CNCF).<sup><\/sup> This transition occurs against a backdrop of intensifying demand for sovereign cloud capabilities and &#8220;Private AI&#8221; 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 &#8220;trust layer&#8221; 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Features<\/h3>\n\n\n\n<p>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.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>CRD-Native Backup Logic:<\/strong> Unlike legacy hypervisor-based snapshots, Velero operates at the Kubernetes API layer, capturing the &#8220;soul&#8221; of the application\u2014its Custom Resource Definitions (CRDs), secrets, and configurations\u2014independently of the underlying storage.<\/li>\n\n\n\n<li><strong>Enhanced etcd Diagnosis and Recovery:<\/strong> Integrated with the new <code>etcd-diagnosis<\/code> and <code>etcd-recovery<\/code> tools, Velero now provides automated paths to repair the Kubernetes control plane when the underlying key-value store becomes corrupted or desynchronized.<\/li>\n\n\n\n<li><strong>Multi-Cloud Mobility Hooks:<\/strong> 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.<\/li>\n\n\n\n<li><strong>CSI Snapshot Integration:<\/strong> 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.<\/li>\n\n\n\n<li><strong>Sovereign-Ready Metadata Masking:<\/strong> 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.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Benefits<\/h3>\n\n\n\n<p>The donation of Velero and its continued integration into VCF 9.0 provides a &#8220;Resilience Dividend&#8221; that balances open-source flexibility with enterprise-grade support.<\/p>\n\n\n\n<p>The primary benefit is <strong>Elimination of Lock-in Anxiety<\/strong>. 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 <strong>Accelerated Disaster Recovery<\/strong>; because Velero understands application topology, it can restore a complex microservices application across different VCF regions faster than a manual &#8220;re-deploy from scratch&#8221; ever could. Furthermore, <strong>Ecosystem Synergy<\/strong> 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.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Use Cases<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Private AI Model Protection:<\/strong> Backing up the training state and vector database configurations for local LLMs, ensuring that a hardware failure doesn&#8217;t result in the loss of weeks of compute-intensive training.<\/li>\n\n\n\n<li><strong>Cross-Cloud Migration:<\/strong> 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.<\/li>\n\n\n\n<li><strong>CI\/CD Pipeline Rollbacks:<\/strong> Integrating Velero into the developer workflow to provide &#8220;automatic save points&#8221; before major application deployments, allowing for instant recovery if a new code push breaks the cluster.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Alternatives<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Kasten by Veeam (K10):<\/strong> 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 &#8220;enterprise admin,&#8221; it carries a significant licensing cost compared to the open-source Velero.<\/li>\n\n\n\n<li><strong>TrilioVault for Kubernetes:<\/strong> 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 &#8220;VCF-first&#8221; organization actually requires.<\/li>\n\n\n\n<li><strong>Native Storage-Level Replication:<\/strong> Relying on vSAN or array-level replication. While extremely fast for data, it is &#8220;application blind&#8221;; it copies the bits but often fails to capture the Kubernetes metadata required to actually <em>run<\/em> the application once it is restored.<\/li>\n\n\n\n<li><strong>Manual &#8220;GitOps&#8221; Recovery:<\/strong> Attempting to rebuild the environment from Git repositories and Helm charts. This is the ultimate &#8220;clean&#8221; recovery, but it is often too slow for production environments because it does not capture the &#8220;state&#8221; (the actual data in the databases) that has accumulated since the last commit.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Alternative Perspective<\/h3>\n\n\n\n<p>While the donation of Velero is framed as a community win, we must apply critical thinking to the <strong>&#8220;Strategic Abandonment&#8221; Theory<\/strong>. Is Broadcom truly fostering community growth, or is it reducing its internal R&amp;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\u2019s development could fragment or slow down, leaving VCF users with a &#8220;stagnant standard.&#8221; Furthermore, we must question the <strong>&#8220;Complexity Paradox&#8221;<\/strong>\u2014Velero is notoriously difficult to configure compared to commercial tools. By making it the &#8220;standard&#8221; for VCF, is Broadcom inadvertently forcing infrastructure teams to become &#8220;Velero engineers&#8221; just to maintain basic data protection? Finally, we must ask if <strong>&#8220;Universal Portability&#8221;<\/strong> is actually a myth; even with Velero, the differences in underlying networking (NSX vs. VPC) often make true &#8220;cross-cloud&#8221; restores a manual, error-prone nightmare.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Final Thoughts<\/h3>\n\n\n\n<p>The move to the CNCF is a masterstroke of &#8220;coopetition.&#8221; By relinquishing control of Velero, Broadcom has made it the &#8220;Linux of Kubernetes Backup.&#8221; 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 &#8220;owns&#8221; the code, but who &#8220;orchestrates&#8221; the outcome.<\/p>\n\n\n\n<p><strong>Source URL:<\/strong> <a target=\"_blank\" rel=\"noreferrer noopener\" href=\"https:\/\/blogs.vmware.com\/cloud-foundation\/2026\/05\/01\/broadcom-donates-velero-to-cncf\/\">https:\/\/blogs.vmware.com\/cloud-foundation\/2026\/05\/01\/broadcom-donates-velero-to-cncf\/<\/a> (and related technical disclosures)<\/p>\n\n\n\n<p><\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Publish Date: May 1, 2026 Executive Overview In a strategic move that fundamentally reshapes the Kubernetes data protection landscape, Broadcom has officially donated Velero\u2014the industry-standard open-source tool for Kubernetes backup and disaster recovery\u2014to the Cloud Native Computing Foundation (CNCF). This transition occurs against a backdrop of intensifying demand for sovereign cloud capabilities and &#8220;Private AI&#8221; [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"elementor_theme","format":"standard","meta":{"footnotes":""},"categories":[20],"tags":[25,26,29],"class_list":["post-3822","post","type-post","status-publish","format-standard","hentry","category-vmware-news","tag-ai","tag-aws","tag-google-cloud"],"_links":{"self":[{"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/3822","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/comments?post=3822"}],"version-history":[{"count":4,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/3822\/revisions"}],"predecessor-version":[{"id":3826,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/posts\/3822\/revisions\/3826"}],"wp:attachment":[{"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/media?parent=3822"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/categories?post=3822"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cloudobjectivity.co.uk\/index.php\/wp-json\/wp\/v2\/tags?post=3822"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}