As former #bitnami #keycloak user we now managed to move away:

https://domaindrivenarchitecture.org/

#DevOps #c4k #clojure #k8s

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

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