Merge pull request #10124 from shubham-pampattiwar/site/cncf-sandbox-blog-post

Site: add blog post for Velero joining CNCF Sandbox
2026-08-03 22:06:07 +00:00 · 2026-07-30 13:02:15 -07:00
parent 95e76381fd 96bf9e2ec1
commit 0c2b588f5a
1 changed files with 69 additions and 0 deletions
@@ -0,0 +1,69 @@
+---
+title: "Velero Joins the CNCF Sandbox"
+excerpt: Velero has been accepted into the Cloud Native Computing Foundation as a Sandbox project, bringing Kubernetes-native backup and disaster recovery under vendor-neutral, community-driven governance.
+author_name: Shubham Pampattiwar
+slug: Velero-Joins-CNCF-Sandbox
+categories: ['velero','announcements']
+image: /img/cncf-color.svg
+tags: ['Velero Team', 'Shubham Pampattiwar', 'CNCF']
+---
+
+![CNCF Logo](/img/cncf-color.svg)
+
+We are excited to announce that Velero has been accepted into the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/) as a Sandbox project. This marks a significant milestone for the project, placing Velero under vendor-neutral, community-driven governance alongside other foundational cloud native tools.
+
+The CNCF Technical Oversight Committee (TOC) accepted the [Sandbox application](https://github.com/cncf/sandbox/issues/457), and the transition was formally announced at KubeCon + CloudNativeCon Europe 2026 in Amsterdam.
+
+## What This Means
+
+Joining the CNCF Sandbox means Velero is now governed by the same open, vendor-neutral principles that guide projects like Kubernetes, Prometheus, and Envoy. In practice, this means:
+
+- **Vendor-neutral governance**: No single company controls the project roadmap. Decisions are made through consensus-based processes with supermajority voting.
+- **Community-driven development**: The project's direction is shaped by its maintainers and contributors, who represent multiple organizations.
+- **Long-term sustainability**: CNCF provides a neutral home that ensures the project's continuity regardless of changes in any single company's priorities.
+
+For existing Velero users, nothing changes in how you use the tool. Velero continues to operate at the Kubernetes API layer, providing backup, restore, disaster recovery, and migration capabilities for your clusters and applications.
+
+## Our Journey
+
+Velero's journey began at Heptio, the Kubernetes company founded by Joe Beda and Craig McLuckie, where it was originally known as Ark. After VMware acquired Heptio in 2019, the project continued to grow under VMware's stewardship. Following Broadcom's acquisition of VMware, the decision was made to contribute Velero to the CNCF, ensuring the project's future under community governance.
+
+Throughout these transitions, one thing has remained constant: a growing and engaged open source community. Today, Velero has over 10,000 GitHub stars, 1,500+ forks, 500M+ Docker Hub pulls, and is used by organizations across industries for Kubernetes data protection.
+
+We are grateful to Broadcom for contributing Velero to the CNCF and to everyone who has contributed to the project over the years.
+
+## Current Maintainers
+
+Velero is maintained by engineers from multiple organizations, reflecting the project's vendor-neutral nature:
+
+| Maintainer | GitHub | Affiliation |
+|---|---|---|
+| Daniel Jiang | [@reasonerjt](https://github.com/reasonerjt) | Broadcom |
+| Wenkai Yin | [@ywk253100](https://github.com/ywk253100) | Broadcom |
+| Xun Jiang | [@blackpiglet](https://github.com/blackpiglet) | Broadcom |
+| Yonghui Li | [@Lyndon-Li](https://github.com/Lyndon-Li) | Broadcom |
+| Scott Seago | [@sseago](https://github.com/sseago) | Red Hat (OpenShift) |
+| Shubham Pampattiwar | [@shubham-pampattiwar](https://github.com/shubham-pampattiwar) | Red Hat (OpenShift) |
+| Tiger Kaovilai | [@kaovilai](https://github.com/kaovilai) | Red Hat (OpenShift) |
+| Anshul Ahuja | [@anshulahuja98](https://github.com/anshulahuja98) | Microsoft (Azure) |
+
+## What's Next
+
+Joining the CNCF Sandbox is the beginning of a new chapter for Velero. Here is what we are focused on:
+
+- **Growing the community**: We want more contributors, more adopters, and more voices shaping the project's direction. Whether you are a user, operator, or developer, there is a place for you in the Velero community.
+- **Strengthening the project**: We are continuing to improve Velero's core capabilities around backup performance, data protection, and ecosystem integration.
+- **Path to Incubation**: Our goal is to demonstrate the community health, adoption, and maturity needed to advance to CNCF Incubation status.
+
+## Get Involved
+
+We welcome contributions of all kinds -- code, documentation, bug reports, feature requests, and feedback.
+
+- **Slack**: Join [#velero-users](https://kubernetes.slack.com/messages/velero) and [#velero-dev](https://kubernetes.slack.com/messages/velero-dev) on Kubernetes Slack
+- **GitHub**: [github.com/velero-io/velero](https://github.com/velero-io/velero)
+- **Community Meetings**: We hold bi-weekly community meetings alternating between US/Europe and US/Asia-friendly time zones. See the [community page](https://velero.io/community/) for details.
+- **LinkedIn**: Follow us at [Project Velero](https://www.linkedin.com/company/project-velero)
+- **Twitter/X**: [@projectvelero](https://twitter.com/projectvelero)
+- **Contributing**: Check out our [contribution guide](https://velero.io/docs/main/start-contributing/) to get started.
+
+We are excited about this new chapter and look forward to building the future of Kubernetes data protection together with the community.