In a move that underscores the growing importance of community-driven development for cloud-native tools, Broadcom has donated Velero—a Kubernetes-native backup and restore project—to the Cloud Native Computing Foundation (CNCF) as a Sandbox project. This transition ensures that Velero will now be governed by an open community, fostering broader collaboration and innovation. Below, we answer key questions about this donation, what Velero does, and what it means for Kubernetes users.

What is Velero and what problem does it solve?

Velero is an open-source tool designed specifically for Kubernetes environments. It provides a robust solution for backing up, restoring, and migrating entire cluster states. The primary problem Velero addresses is the challenge of protecting Kubernetes workloads and data in a dynamic, containerized ecosystem. Traditional backup methods often fail because they rely on hypervisor or storage-level snapshots that don't understand Kubernetes objects like Deployments, Services, or PersistentVolumeClaims. Velero operates at the Kubernetes API layer, capturing cluster state using Custom Resource Definitions (CRDs). This allows it to backup not just data but also configuration, metadata, and the relationships between resources. For operators, this means they can reliably recover from disasters, migrate clusters between environments, or clone setups for testing—all with minimal manual intervention. By being Kubernetes-native, Velero ensures that backups are consistent, portable, and automatically adjusted as the cluster evolves.

Why did Broadcom donate Velero to the CNCF?

Broadcom's decision to donate Velero to the CNCF reflects a strategic shift toward community governance for the project. By placing Velero under the CNCF umbrella—specifically as a Sandbox project—Broadcom aims to accelerate its adoption and development. The CNCF provides a neutral home where contributors from various organizations can collaborate without vendor lock-in. This move is similar to how other successful cloud-native tools like Kubernetes itself started as community projects. Broadcom retains the benefit of having Velero enhanced by external contributions, while the community gains transparency and influence over the roadmap. For users, this donation signals long-term stability: the project will not disappear if a single company changes priorities. It also opens doors for integrations with other CNCF projects (e.g., Prometheus, Helm, or Knative) and ensures that Velero follows open governance practices, including a clear contributor process and community-driven decision-making.

How does Velero perform backups differently from traditional methods?

Unlike traditional backup tools that rely on hypervisor snapshots or storage-level replication, Velero works entirely within the Kubernetes API layer. It uses Custom Resource Definitions (CRDs) to track cluster state—including all Kubernetes objects such as Pods, ConfigMaps, Secrets, and PersistentVolumeClaims. When a backup is triggered, Velero first gathers metadata about these resources, then orchestrates the creation of volume snapshots via cloud provider plugins (e.g., AWS EBS, Azure Disk, GCP Persistent Disk). This approach has several advantages: First, it ensures that backups are application-aware—Velero knows which volumes belong to which Deployment and can coordinate snapshot timing. Second, it makes backups highly portable: you can restore a cluster to a different cloud provider or on-premises environment. Third, it reduces overhead because only changed resources are backed up (incremental backups). The result is a backup that contains both the configuration and data, making restore operations straightforward and reliable. For more on the benefits, see Who can benefit from Velero.

What does it mean for Velero to be a CNCF Sandbox project?

The CNCF Sandbox is the entry-level stage for projects that are still maturing but show potential for cloud-native ecosystems. By joining as a Sandbox project, Velero gains visibility, access to CNCF resources (like infrastructure for CI/CD), and a path to become an Incubating or even Graduated project later. For the community, this status indicates that the project has passed an initial vetting and is open to external contributions under a neutral governance model. Sandbox projects typically have a limited but growing set of contributors and users. They benefit from the CNCF's support in areas like marketing, legal, and community building. For Velero, this means it can attract more developers, improve documentation, and integrate with other CNCF projects. It also reassures enterprises that the project is aligned with open standards and will not suddenly become proprietary. This is a positive step before moving to higher maturity levels, as described in the future implications.

Who can benefit from Velero and how can they get started?

Velero is valuable for any organization running Kubernetes in production. DevOps teams, platform engineers, and SREs (Site Reliability Engineers) can use it to automate backup and disaster recovery workflows. Cloud-native developers benefit from Velero's ability to clone environments for testing or staging, making it easier to debug issues. Enterprises that need to comply with data protection regulations (e.g., GDPR, SOC 2) find Velero's consistent snapshots and restore testing invaluable. Managed service providers (MSPs) can leverage Velero for multi-tenant backup strategies. Getting started is straightforward: you can deploy Velero using its CLI or Helm chart, configure a cloud provider plugin for volume snapshots, and define scheduled backup policies. The official documentation provides step-by-step guides. Since joining the CNCF, the community has also started hosting contributor meetups and office hours, making it easier for newcomers to ask questions and contribute. For a deeper understanding of its architecture, refer to How Velero performs backups.

What are the future implications of this donation for the Kubernetes ecosystem?

Broadcom's donation of Velero to the CNCF is likely to accelerate adoption and innovation in Kubernetes backup and disaster recovery. With community governance, Velero can now evolve more rapidly through contributions from a diverse set of stakeholders. This may lead to better integrations with emerging CNCF projects (e.g., backstage for service catalogs, Kyverno for policy management) and deeper support for multi-cloud scenarios. As more organizations adopt Velero, it could become the de facto standard for Kubernetes backup, much like Prometheus for monitoring. The Sandbox status also paves the way for a graduated project that meets higher standards of security, documentation, and stability. For end users, the immediate benefit is increased confidence that Velero will remain open and actively maintained. Long-term, we may see the community developing advanced features such as backup verification, cross-cluster migration automation, or even intelligent restoration prioritization. In summary, the donation strengthens the cloud-native ecosystem by turning a proven tool into a shared resource.