In a significant move for open-source cloud-native tools, Broadcom has donated the Velero project to the Cloud Native Computing Foundation (CNCF). This shift places the Kubernetes backup and restore tool under community governance. Below, we answer key questions about this transition and what it means for users and developers.

What is Velero and what does it do?

Velero is an open-source tool designed for backing up, restoring, and migrating Kubernetes clusters and their persistent data. It operates natively within the Kubernetes API layer, capturing the entire state of a cluster—including namespaces, deployments, services, and volumes—through Custom Resource Definitions (CRDs). This Kubernetes-native approach means Velero integrates seamlessly with existing workflows, allowing administrators to schedule backups, perform disaster recovery, and even migrate workloads between clusters without relying on hypervisor or storage-specific snapshots. By storing backup data in object storage backends like Amazon S3 or Google Cloud Storage, it provides a portable and vendor-neutral solution for protecting Kubernetes environments.

Why did Broadcom donate Velero to CNCF?

Broadcom decided to donate Velero to CNCF to foster broader community involvement and ensure the project's long-term sustainability. By moving to a neutral open-source foundation, the project benefits from diverse contributor perspectives, transparent governance, and a shared roadmap. This aligns with the industry trend of placing critical infrastructure tools under community oversight, reducing dependency on a single vendor. The donation also signals Broadcom's commitment to supporting the cloud-native ecosystem, as CNCF provides a trusted home for projects that drive Kubernetes adoption. For users, this means Velero's development will be more collaborative, accelerating innovation and bug fixes while maintaining compatibility with the evolving Kubernetes landscape.

How does Velero work with Kubernetes?

Velero operates at the Kubernetes API layer, meaning it interacts directly with the cluster's control plane rather than with underlying infrastructure. It uses Custom Resource Definitions (CRDs) to define backup, restore, and schedule operations as Kubernetes resources. When a backup is triggered, Velero queries the Kubernetes API server to gather cluster state—such as resource manifests—and then captures volume snapshots via CSI drivers or native cloud provider interfaces. This approach ensures that Velero is portable across any Kubernetes distribution and cloud provider, as it relies solely on standard API extensions. The tool also supports hooks for running custom commands before or after backup/restore operations, giving administrators fine-grained control over data consistency and application behavior during downtime.

What is the significance of becoming a CNCF Sandbox project?

CNCF Sandbox is an entry-level stage for early-stage projects that shows they are on track to become viable cloud-native solutions. For Velero, this status provides visibility, a neutral governance structure, and access to CNCF resources like marketing support and community events. It also signals to users and potential contributors that the project meets CNCF's criteria for openness and quality. While Sandbox projects are not yet mature, the designation often attracts new contributors and accelerates adoption. Over time, Velero could progress to Incubating or Graduated stages, gaining additional endorsements. This donation effectively transforms Velero from a Broadcom-controlled tool into a community asset, encouraging wider use and third-party integrations within the Kubernetes ecosystem.

How does Velero differ from traditional backup solutions?

Traditional backup solutions often work at the hypervisor, storage, or application layer, requiring specific integrations and often resulting in vendor lock-in. Velero, in contrast, is purpose-built for Kubernetes. It captures cluster state and data at the API level, making it container-aware and cloud-agnostic. Instead of relying on VM snapshots or storage array clones, Velero uses Kubernetes-native primitives like CRDs and CSI snapshots. This allows it to backup not just persistent volumes but also the cluster's configuration, including RBAC policies and network policies. Additionally, Velero supports incremental backups and retention policies, optimizing storage usage. Its migration capabilities let users move workloads between clusters (e.g., from on-premises to cloud) with minimal disruption—a feature rarely offered by traditional backup tools.

What impact will this donation have on the Kubernetes ecosystem?

The donation strengthens the Kubernetes ecosystem by ensuring a critical backup tool remains open and community-driven. It encourages more organizations to contribute to Velero's development, leading to faster feature releases and broader compatibility with other CNCF projects like Prometheus or Knative. For end users, this means increased confidence in using Velero for production workloads, as the CNCF governance provides oversight and long-term commitment. The move also promotes interoperability: with community governance, Velero is more likely to adopt standards like CSI and OPA, integrating seamlessly with the wider cloud-native stack. Furthermore, this donation sets a precedent for other vendors to contribute their tools to neutral foundations, fostering a healthier open-source landscape.

What are the next steps for Velero development?

With CNCF stewardship, Velero's roadmap will now be shaped by the community through open discussions and contributions. Immediate priorities include refining the project's documentation, improving test coverage, and expanding support for additional backup targets like multiple object storage providers. There is also ongoing work to enhance performance for large-scale clusters and to integrate Velero with other CNCF tools, such as Crossplane for custom resources or Flagger for canary deployments. Broadcom remains a contributor but no longer holds sole control. New maintainers are expected to emerge from the community. For developers interested in contributing, the project's repository already lists good first issues and detailed contribution guidelines. The CNCF Sandbox stage is the first step; the ultimate goal is to achieve Incubating status, which requires demonstration of sustained community growth and production usage.