Operator Helm chart - Bitnami policy changes #1915
Replies: 6 comments 5 replies
-
|
I don't think we'll get an answer, because it seems RabbitMQ is developed by VMWare (aquired by Broadcom 2 years ago), same company that doing the change in Bitnami Helm charts and docker images. 
|
Beta Was this translation helpful? Give feedback.
-
|
You and others in this thread did get several answers straight from the RabbitMQ core team below, despite the fact that responding potentially carries a risk to the individual members of our team. |
Beta Was this translation helpful? Give feedback.
-
|
My guess is that even if we get an answer, it will be that it will be part of the secure images subscription ($6k per month for 12 months) :/ |
Beta Was this translation helpful? Give feedback.
-
|
So what this means is basically, that we'll have to not only find a replacement for the operator chart, but also for the base images of rabbitmq itself too? |
Beta Was this translation helpful? Give feedback.
-
|
@mbauer-dilt the main RabbitMQ image is community maintained, and has always been. Team RabbitMQ did contribute but we are not the maintainers of that image. |
Beta Was this translation helpful? Give feedback.
-
Means that the ones over there are final or at least won't be changed anytime soon.. Worth noting that even if they would put the image back on the free/public catalog, it's not intended for production use and only has the The images I've found are:
For the charts, haven't found any that is decently popular or not closed source. https://github.com/trueforge-org/truecharts seems to be an alternative if you want to put your trust again in a third-party, but RabbitMQ is (currently) missing there. However, really worth remembering that RabbitMQ is owned by the same company that switched Bitnami from free to a subscription based plan... |
Beta Was this translation helpful? Give feedback.
-
|
The most popular RabbitMQ image by far is a 3rd party. |
Beta Was this translation helpful? Give feedback.
-
As a RabbitMQ contributor of 15 years, I do not appreciate this speculative tone. RabbitMQ has been an open source project since at least Feb 2007 (if we take the 1.0 release for starting point). Even though Broadcom contributes well over 90% of R&D, there are at least four companies that contribute regularly, and three contribute to virtually every patch release, leave alone minors or majors. RabbitMQ remains an MPL2-licensed data service in a world where everyone and their grandma have gone BSL, SSP, and so on. This has been the case for over 18 years now (well, first as MPL1 since RabbitMQ pre-dates MPL2) and those are facts, not a random speculation from an anonymous account on GitHub. |
Beta Was this translation helpful? Give feedback.
-
|
Hello folks 👋 Before I express my opinions, I want to be very clear that this reply does not represent Broadcom, is not an official answer, I do not speak in the name of Broadcom, and all statements are my sole personal opinions on the matter. As shared earlier in the discussion, VMware is owned by Broadcom, and Broadcom is the main sponsor of RabbitMQ. Broadcom is also the sole sponsor of RabbitMQ Kubernetes operators. You'll understand that our team is highly unlikely to turn against the company that pays our wages, and provide a free, open, alternative. However, not all is dire. RabbitMQ official container image is controller by Docker. We collaborate with them from time to time, and some of our team members actively follow the GitHub repository for the official Docker image. This gives high confidence that RabbitMQ container image will remain open source and maintained for the time being (why would Docker stop maintaining their library images?) Bitnami Helm chart happens to provide a re-built container image of RabbitMQ, with the claim that it's updated periodically and has less CVEs, and other goodies I don't remember now. However, there's nothing special about that container image, it's just rabbit running with different defaults. In addition to that, Bitnami Helm charts have a feature to customise what container image is rendered in the final manifests.
I personally think this depends on what your business needs are. Do you want fast CVE patching responses? Do you want a company behind you to provide support? All those sound like enterprise needs that should pay the Bitnami premium service. If you are not willing to pay for those, then attending those needs become your responsibility and then becomes a matter of cost of ownership vs cost of paying Bitnami premium service.
I want to re-state that this response are my own opinions and I do not speak in the name of Broadcom. That being said, I think it's highly unlikely (almost impossible), that RabbitMQ becomes closed source. I think the same of our Kubernetes operators. Why? Just look at Broadcom offerings of RabbitMQ: one of them is long term support for OSS rabbit. |
Beta Was this translation helpful? Give feedback.
-
I'll just add that I am a maintainer of that image 😸 |
Beta Was this translation helpful? Give feedback.
-
As stated multiple times earlier, the most popular RabbitMQ image by far has always been a community project (led by Docker, Inc. at first). You are welcome to maintain any Helm chart you want, using that image as the base. Our team's recommended way of deploying RabbitMQ to Kubernetes is an Operator, and that's been the case for years. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
With the pending end of public updates for the Bitnami helm charts (including the one for the operator), an alternative should be found.
Describe the solution you'd like
Ideally some effort should be made to either find a partner willing to continue maintenance of the helm charts.
Given that Bitnami helm charts will stay available, with only the images they refer to being made private, charts could be simply mirrored with image refs being changed. This would reduce maintenance effort to updating the image refs.
Describe alternatives you've considered
There are not really any besides letting the operator helm chart die, which would be a real shame for those that have come to rely on helm.
Additional context
The link to the bitnami announcement
Beta Was this translation helpful? Give feedback.
All reactions