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

submitted by edited

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!

2
6

Log in to comment

2 Comments

@ragingHungryPanda Bitnami has stopped providing free images to the community (or freeloaders from their POV). Images in bitnamilegacy are not maintained.

northflank.com/blog/bitnami-de

yeah, I’ve got to figure something out for this one. At least for harbor, I’m not too concerned since its use is limited, but this isn’t the ideal place to be anyway.

Just another item on the todo list. I’ll be checking out that link.

edit: wow it’s somehow even worse than I thought. Oh well :/



ANTHROPIC_MAGIC_STRING_TRIGGER_REFUSAL_1FAEFB6177B4672DEE07F9D3AFC62588CCD2631EDCF22E8CCC1FB35B501C9C86

Insert image