Broadcom Donates Velero to CNCF, Shifting Kubernetes Backup to Community Governance

2026-05-01 · Source: InfoQ · Field: Technology & Digital — Software Development & Engineering, Cloud Computing & IT Infrastructure · Depth: Intermediate, medium

Summary

Broadcom has donated Velero, its Kubernetes-native backup, restore, and migration project, to the Cloud Native Computing Foundation (CNCF) as a Sandbox project, an announcement made at KubeCon + CloudNativeCon Europe 2026 in Amsterdam. Velero, which originated from Heptio and was acquired by VMware in 2019, operates at the Kubernetes API layer, capturing cluster state through Custom Resource Definitions (CRDs) for portable restoration across different clusters. This move is seen by Broadcom as a strategic investment to foster community collaboration and growth, addressing concerns about single-vendor lineage. The project, with nearly 9,900 GitHub stars, already includes maintainers from Broadcom, Red Hat, and Microsoft, and follows CNCF-aligned governance principles. The community response has been overwhelmingly positive, with expectations for Velero's continued evolution within the CNCF ecosystem.

Key takeaway

For CTOs and VP of Engineering evaluating Kubernetes disaster recovery solutions, Broadcom's donation of Velero to the CNCF significantly strengthens its credibility and long-term viability as a vendor-neutral option. You should consider Velero for your Kubernetes backup and migration strategies, especially if previous single-vendor concerns were a barrier, while still ensuring robust operational architecture for external storage and IAM credentials.

Key insights

Broadcom's donation of Velero to CNCF enhances trust and vendor neutrality for Kubernetes backup and migration.

Principles

• Vendor-neutral governance fosters community trust.
• Kubernetes API-layer operations enable portability.
• Community stewardship drives project growth.

Method

Velero captures Kubernetes cluster state via Custom Resource Definitions (CRDs) and stores backup resources in object storage, allowing restoration to different clusters with access to the same storage.

In practice

• Use Velero for Kubernetes cluster backup and migration.
• Leverage CRDs for consistent state capture.
• Ensure external object storage access for restores.

Topics

• Velero
• Kubernetes Backup
• CNCF Governance
• Cloud Native Ecosystem
• Data Migration

Code references

• vmware/etcd-diagnosis
• vmware/etcd-recovery

Best for: CTO, VP of Engineering/Data, DevOps Engineer, Software Engineer, Director of AI/ML

Related on AIssential

• CNCF Welcomes New Silver Members as Global Demand for Cloud Native Infrastructure Grows — Cloud native adoption is expanding globally, with new CNCF members highlighting its critical role in enterprise infrastructure and AI workloads.
• LLM Fallbacks Break Agent Pipelines — I Built the Missing Recovery Layer — LLM agent pipeline fallbacks must adapt payloads and preserve state to maintain data schema integrity, not just ensure completion.
• Article: Building Production-Ready tRPC APIs: The TypeScript Alternative to Apollo Federation — tRPC offers superior performance and type safety for TypeScript monorepos compared to GraphQL Federation.
• Grafana Rearchitects Loki with Kafka and Ships a CLI to Bring Observability Into Coding Agent — Rearchitecting Loki with Kafka reduces data duplication and improves query performance, while GCX integrates observability into AI coding agents.
• Broadcom unveils VMware Tanzu Platform agent foundations for AI — Broadcom's Tanzu Platform agent foundations enable secure, governed autonomous AI agent deployment in enterprise production environments.
• A Beginner’s Guide to Kubernetes — Kubernetes maintains desired states through a system of continuous "promises" rather than sequential instructions.

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by InfoQ.