🔊 Notice about LTS branches and pull rates in Docker Hub

[carrodher]

Starting December 10th, 2024, only the latest stable branch of applications deployed by Bitnami Helm charts will receive updates in the free Bitnami catalog. Previous versions already released will not be deleted. They are still available to pull from DockerHub.
For example, for PostgreSQL, only branch 17 (the latest stable version) will be maintained in the free catalog. Other upstream-supported branches, such as 13, 14, 15, and 16, will be exclusively available through Bitnami Premium.

Beginning on December 16th, 2024, all free Bitnami Helm charts and containers will be subject to standard pull-rate limits and pull caps in Docker Hub.

To continue accessing up-to-date releases of all the upstream-supported branches and to pull without any limitations, you can upgrade to Bitnami Premium. Please check the Bitnami Premium page in our partner Arrow Electronics for more information.

[gusfcarvalho]

Out of curiosity, Was this something imposed by docker.io agreements, or was it a business decision from VMware/broadcom?

is there anywhere where the rationale behind it is available?

[thesuperzapper]

I would like to urgently request Bitnami/VMWare (@Maarc, @ridruejo, @carrodher) work with Docker (@justincormack, @girisreenivas) to keep the no-rate-limits on a few critical images so Kubernetes clusters don't break a few days before Christmas all over the world (and with only 3 days notice).

Specifically, the Bitnami images which contain clients like kubectl, bash, mysql are used by countless open-source project and enterprises because they don't have pull limits. Suddenly introducing limits will break many important things like CronJobs and other scripts, because they are pulled more frequently than other images.

Please reconsider adding the rate-limits on the following critical images, at least till after the holidays:

• docker.io/bitnami/kubectl
• docker.io/bitnami/os-shell
• docker.io/bitnami/minio-client
• docker.io/bitnami/azure-cli
• docker.io/bitnami/postgresql
• docker.io/bitnami/mysql
• docker.io/bitnami/redis

But if you only do one, please do docker.io/bitnami/kubectl as that one will cause sooo many problems, as it's effectively the standard kubectl image.

[d-lebed]

I didn't ask for this for Christmas.

[tuananh]

while I can understand the decision, doing this with such short notice and right before Christmas is just sad.

[stefanprodan]

But if you only do one, please do docker.io/bitnami/kubectl as that one will cause sooo many problems, as it's effectively the standard kubectl image.

The standard image of kubectl is provided by the Kubernetes project and can be found at registry.k8s.io/kubectl:v1.32.0, it goes back to v1.28.0.

[jkroepke]

Keep in mind that if you are using the legacy Helm index (https://charts.bitnami.com/bitnami/index.yaml), your deployments are still subject to standard Docker Hub rate limits because the index also points to Docker Hub.

[bradmbock]

Hi, product manager for Bitnami here. We hear you and realize the timing is not ideal. Unfortunately we are obligated to make this change as quickly as possible due to business and partner requirements. However, in an effort to minimize impact on this community we are now implementing a plan to roll out these changes incrementally and not fully implement until you get through the holiday break.

This morning we have introduced the changes temporarily for three hours to measure the effect. We will then implement a second 12-hour temporary change on Thursday December 19th. Finally, the permanent change will take effect on Monday, January 6th 2025.

Thank you for the feedback. For more context about these changes, and our continued commitment to providing the Bitnami catalog for our community, you can read more in our recent blog post.

[ydixken]

Unfortunately we are obligated to make this change as quickly as possible due to corporate greed.

There, I fixed it for you.

[max06]

Time to get rid of bitnami images, I guess. ¯_(ツ)_/¯

Edit: I definitely wish you good luck with the upcoming licencing issues!

[gusfcarvalho]

Time to get rid of bitnami images, I guess. ¯_(ツ)_/¯

Edit: I definitely wish you good luck with the upcoming licencing issues!

Why would there be any licensing issues?

[max06]

Why would there be any licensing issues?

I'm sure other companies like mongodb love it when vmware sells their software with a hefty price tag.

[mamoit]

Merry christmas everyone!
And a happy on-call duty.

Now seriously, @carrodher can't you delay this decision one month?
Roll it out on the 6th of January or even the 2nd or 3rd (which is a Friday, but still better than this), at least there will be people in the office by then to put out the unexpected fires, it won't have to be the poor people who pulled the short straw and got the christmas/new year's on call duty.

You will save a lot of people a lot of headaches and in return get some kudos for reviewing your decision.

[mamoit]

Ok, aparently the decision has been delayed 👍 thank you!

https://blog.bitnami.com/2024/11/bitnami-premium.html