Broadcom donates Velero to CNCF — and it could reshape how Kubernetes users handle backup and disaster recovery

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Broadcom VMware announced on Monday that it will donate Velero to the CNCF sandbox project, a move the company describes as a way to extend VMware vSphere Kubernetes Service to Kubernetes user organizations in both private and public clouds. 

Taking a cue from user-organization feedback, Broadcom VMware’s expanding integration with open-source options gives users more freedom to mix and match Kubernetes infrastructure support. Broadcom is also expanding the VMware vSphere Kubernetes Service with API compatibility for more third-party open-source suppliers – in addition to its donation of Velero to the CNCF – including F5, Tigera Calico Enterprise, and Kong API Gateway.

During a briefing with the press before the announcement, Broadcom VMware representatives sought to reassure the community that it is ramping up open-source support and contributions — especially for Kubernetes, the largest CNCF project — using KubeCon + CloudNativeCon Europe as the venue to make these announcements. 

With the VMware donation of Velero, more of the open-source community and user organizations can integrate their needs more easily by contributing to the project, with CNCF support as well. That aspect should help the project serve the larger community’s needs as its direct and governance control shifts away from Broadcom. At the same time, for Broadcom, this strengthens its position as a full-stack Kubernetes provider across cloud-native and private cloud spaces.

“Backup and [disaster recovery] is a big pain point for many organizations as they are trying to bring together the new cloud …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://thenewstack.io/broadcom-velero-cncf-kubernetes/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.