Broadcom Donates Velero to CNCF, Shifting Kubernetes Backup to Community Governance
Summary
Broadcom has transitioned the Velero Kubernetes backup, restore, and migration project to the Cloud Native Computing Foundation (CNCF) as a Sandbox project. This move shifts the project from Broadcom/VMware stewardship to a vendor-neutral community governance model.
Key Points
- Velero operates at the Kubernetes API layer, utilizing Custom Resource Definitions (CRDs) to capture cluster state rather than relying on hypervisor or storage-layer snapshots.
- The project is now a CNCF Sandbox project, with a maintainer list that includes Broadcom, Red Hat, and Microsoft.
- Governance follows a consensus-based model featuring supermajority voting and a five-day lazy-consensus review period.
- The tool enables the backup of namespace definitions, Persistent Volume Claims (PVCs), RBAC policies, and other resource configurations as portable Kubernetes objects.
- Operational dependencies remain unchanged, requiring external object storage, valid IAM credential chains, and a functional target cluster for restoration.
- Potential future roadmap items include integration with the CSI Data Management specification for application-aware backups (via pre-snapshot quiescing) and the implementation of Sigstore for signed backup artifacts.
Technical Details
Velero functions by treating external object storage as the source of truth, continuously reconciling backup resources within the cluster against the contents of the configured storage bucket. This design allows for workload migration across different Kubernetes distributions or clusters, provided the target Velero installation has access to the same underlying storage location. The project captures the cluster state through the Kubernetes API, ensuring that resource configurations are stored as portable objects.
While the governance transition does not alter the current runtime architecture, there are unconfirmed technical directions for the project's future. These include the potential development of a centralized control plane to manage backup policies across multiple clusters and the implementation of more advanced application-aware backup capabilities through the CSI Data Management spec.
Impact / Why It Matters
The transition to CNCF governance provides a vendor-neutral framework for organizations that previously avoided standardizing on Velero due to its single-vendor lineage. For platform teams, the operational requirements for managing object storage, IAM, and cluster connectivity remain identical to the previous stewardship model.