Velero Going CNCF Isn't About Backup. It's About Control.

The Velero CNCF backup announcement at KubeCon EU 2026 was framed as an open source governance story. Broadcom contributed Velero — its Kubernetes-native backup, restore, and migration tool — to the CNCF Sandbox, where it was accepted by the CNCF Technical Oversight Committee. Most coverage treated this as a backup story. It isn't. Velero moving to CNCF governance is a control plane story disguised as an open source announcement. And if your team is running stateful workloads on Kubernetes, the distinction between vendor-neutral governance and vendor-independent operations is the architectural decision that sits beneath the headline. What the Velero CNCF Backup Move Actually Means Velero originated at Heptio — founded by Kubernetes co-creators Joe Beda and Craig McLuckie — which VMware acquired in 2019. It's been under VMware, then Broadcom stewardship ever since. The project operates at the Kubernetes API layer, not the storage layer. All backup operations are defined via CRDs ( Backu