Considering volsync instead or in addition to Velero for backups or volumes

https://github.com/backube/volsync

Partly because who knows if broadcom will decide to broadcom all over Velero, and also it is choking on my nextcloud volume

#Kubernetes #Homelab #FuckBroadcom
GitHub - backube/volsync: Asynchronous data replication for Kubernetes volumes

Asynchronous data replication for Kubernetes volumes - backube/volsync

GitHub
The $69 Billion Domino Effect: How VMware’s Debt-Fueled Acquisition Is Killing Open Source, One Repository at a Time

Bitnami’s decision to end its free tier by August 2025 has sparked widespread outrage among developers who rely on its services. This change is part of Broadcom CEO Hock Tan’s strategy …

FastCode

@rachel Wow. Reading it black-and-white like that, it's all really appalling. And those profit margins are just utterly disgusting. None of this was actually necessary in any way, shape or form.

And I had no idea that Bitnami images were so widespread. Most of the time, when the project doesn't offer an image, I just build it myself. Are the Bitnami images that good?

@mmeier @rachel Good? Don’t know. They certainly were a consistent experience and usually worked. Though personally I always steered clear of them.

I had to deal with the fallout of Bitnami images at work the last couple of weeks. Faced some interesting challenges due to Bitnami sometimes having very different approaches compared to other images.

@jana @rachel So it was mostly that all of the Bitnami images worked/were build the same way, so when you know one Bitnami image you know them all?

Consistency as the big benefit?

@mmeier @rachel Kinda, yeah. There are common variables. Mount points are similar. It’s all very predictable. Same goes for the complimentary Bitnami Helm Charts.
@jana @mmeier The helm charts are where people at my org had gotten burned. They had been using helm charts as sub-charts for things like redis/databases. Now the plan is to jettison everything bitnami.