The #MSTDNDK Mastodon instance just migrated away from Bitnami's #Redis helm chart and container images to #Valkey.

#Bitnami and Redis both seem to be exiting the open source community, which could prevent us from staying current, meaning always running the latest versions of the software components that make up this instance.

We understand the need to monetize software, but see that as an opportunity to add premium paid features, not take away existing ones from open source. Doing so will make your potential future customers look for other solutions. Looking at you, #MinIO, Redis and Bitnami.

Please report any issues you might experience as a result of the move to Valkey. So far it looks peachy.

For anyone running web applications in need of #Keycloak as #IdP here is a #Helmfile showing how to run a simple setup. It is supposed to stay #FOSS forever (unlike #Bitnami). Comments, bug reports and PRs are very much appreciated.

https://github.com/starwit/keycloak-helmfile-template

Finally completed a replacement of the Bitnami charts and images we had in a project.
It's no secret that when you do such a thing, you invest way more effort than if you'd need with using their new free versions.
But! They broke a trust to a software provider, they undid literally years spent on delivering all these artifacts.
So, any sane person would rather jump off their shit train, which I did as well.

#Kubernetes #k8s #DevOps #Bitnami

https://github.com/bitnami/charts/issues/35164 - #Bitnami was bought by #Broadcom and is now going closed-source. #images on #Docker Hub are moving to "legacy" and getting abandoned. Or start paying. https://thenewstack.io/broadcom-ends-free-bitnami-images-forcing-users-to-find-alternatives/

Finally migrated all my #Postgres #Bitnami instances over to Crunchy Postgres (k8s) (n = 12) and pgautoupgrade (https://github.com/pgautoupgrade/docker-pgautoupgrade) (docker) (n = 8) and updated all to v18.

Should probably write a blog post about it.

Bitnami is updating some of the their kubernetes helm charts and moving this to a legacy repo

However, not all of the charts seem to be getting updated.

I’m running my own harbor registry for maintaining my own images for www.keyboardvagabond.com and I was working on finishing up this longhorn excessive api call issue when I saw that harbor stopped working.

Essentially, the gist is that they moved certain image references to the bitnamilegacy repository instead of bitnami, but the harbor helm chart didn’t get the updates, so the images failed to pull because they “disappeared” and updating the the latest helm version didn’t solve it.

Essentially, for now what I had to do was go to the default values modal and search for “repository” and make sure that I had an entry under earch part for image.repository where the value was bitnamilegacy/<failing image name without tag>.

This took me a while to figure out and I hope this helps someone!

https://piefed.keyboardvagabond.com/c/selfhosted/p/148402/bitnami-is-updating-some-of-the-their-kubernetes-helm-charts-and-moving-t

Bitnami is updating some of the their kubernetes helm charts and moving this to a legacy repo

However, not all of the charts seem to be getting updated.

I’m running my own harbor registry for maintaining my own images for www.keyboardvagabond.com and I was working on finishing up this longhorn excessive api call issue when I saw that harbor stopped working.

Essentially, the gist is that they moved certain image references to the bitnamilegacy repository instead of bitnami, but the harbor helm chart didn’t get the updates, so the images failed to pull because they “disappeared” and updating the the latest helm version didn’t solve it.

Essentially, for now what I had to do was go to the default values modal and search for “repository” and make sure that I had an entry under earch part for image.repository where the value was bitnamilegacy/<failing image name without tag>.

This took me a while to figure out and I hope this helps someone!

https://piefed.keyboardvagabond.com/c/selfhost/p/148400/bitnami-is-updating-some-of-the-their-kubernetes-helm-charts-and-moving-t

Moar adventures in #selfhosting for #keyboardvagabond! I think that I finally got the longhorn too-many-s3-calls networking issue resolved https://blog.keyboardvagabond.com/michael-dileos-software-and-tech-blog/longhorns-backup-cost-savings-or-not-getting-surprise-bills

I also found that the #bitnami #helmchart for #harborRegistry didn't get updated with the latest migration they did, so I had to find out that they moved their repositories to `bitnamilegacy` and update my helm chart. That took a while to figure out why the image pulls failed!

@selfhosted
@selfhosting
#kubernetes

#Bitnami/#Broadcom just freaking... deleted all of their old/free #Docker images - and now my #PostgreSQL/#MariaDB/#MySQL deployments have just lost the ability to re-pull their images, which I don't have stored locally anywhere atm. What the actual.. fuck, Broadcom?

---

edit: hope?

🔗 https://hub.docker.com/u/bitnamilegacy

#docker #Bitnami ist für mich endgültig gestorben.

Erst verlieren neuere #PHP Versionen #XDebug, und jetzt für #Postgres, #Apache , ....

bitnami/apache:latest not found: manifest unknown: manifest unknown

F*uck you, so geht's nicht. Wieder sinnlose arbeit für mich.

#Distroless #OCI containers to replace #Bitnami images. Governments explore different options: #Nix_Flakes custom builds, community images.

Read my take and another option based on #Fedora at https://blog.riemann.cc/digitalisation/2025/10/26/distroless-containers-nix-flakes-vs-fedora/

What is your view?

#opensuse #podman #NixOS #digitialsovereignty #supplychain #NIS2

https://backupscale.com/posts/drubernetes-v2-bitnami-to-official-mariadb-operator/
#Drubernetes #Kubernetes #Drupal #Terraform #MariaDB #Bitnami #OpenSource #IaC #Helm #CloudComputing #Licensing

Oublié de corriger les #helm chart de #Mastodon après le coup de poignard dans le dos de #Bitnami... Base PostgreSQL en l'air. Corrigé avec les images "legacy" mais il va falloir que je fasse en sorte de sortir de l'impasse qu'ils nous ont imposée.
Moralité, je finirai de faire mon repo avec mes propres helm chart pour les services importants (maria en mode Galera / Monoservice, Postgres, FerretDB pour remplacer Mongo...) et bye bye les enfoirés qui ont pourri le libre et l'open source.

:k8s:​ :postgresql:​ For those looking for an easy and well maintained PostgreSQL helm chart that isn't bitnami, what do you use now that bitnami is slowly closing source everywhere?

#bitnami #postgres #postgresql #helm #kubernetes

On a related note - no more #vmware or #bitnami , anything.

#Bitnami deleted all the tags in their bitnami/fluent-bit registry in docker-hub.
Thanks a bunch, I just got some free chaos engineering.
https://hub.docker.com/r/bitnami/fluent-bit

On the topic of #Bitnami choosing to block free access to their container builds of open source software: there's a lesson there. Something about putting all your eggs in someone's else's basket or something like that. Also, taking free things for granted. I know you can get around it, but it's a temporary workaround and not a solution, nor a Plan B.

The loss of the #Bitnami #OpenLDAP image really hurts: https://hub.docker.com/r/bitnami/openldap. I only use it for unit testing, but getting that set up the first time was a trial. I really don't want to roll my own container for that.

Ah, heute scheint der Tag zu sein, an dem ich rausfinde, wo ich überall noch #bitnami Container Images laufen habe.

#ImagePullBackOff

Headsup - Bitnami have just removed a load of docker tags/images from Docker Hub. If you use any Bitnami images it's worth checking that you're still going to be able to start new containers and update image references.

We'd built a system using Redis, and it's now broken because of this.

We'd normally push third-party images to our own registry but it looks like someone forgot to do that in this case (that someone being me). Don't be like me.

#docker #tech #redis #bitnami #kubernetes #aws #gke #cloud