Live data from Hacker News

Broadcom to discontinue free Bitnami Helm charts

github.com

71–80 of 142 posts

Re: Broadcom to discontinue free Bitnami Helm charts

#71
post #35

Broadcom gonna Broadcom. Don't anthropomorphize the lawnmower.

The source of this great quote, from the wonderful Bryan Cantrell: https://youtu.be/-zRN7XLCRhc

Said about Larry Ellison (who recently gave $6B to his son to buy CBS, and likely turn it into another ultra-wealthy right-wing mouthpiece rag).

But damn oh damn does Broadcom feel like a good fit for this statement.

Re: Broadcom to discontinue free Bitnami Helm charts

#72

Maybe this will finally break me of my habit of using helm charts, period.

I’ve never used Helm charts. I learned K8S in a shop in which kustomize is the standard and helm is a permitted exception to the standard, but I just never felt any reason to learn helm. Am I missing out? Sometimes the limitations of kustomize annoy me, but we find ways to live with them

One thing I haven't seen mentioned in comment. Dunno if Kustomize has something here. But: Helm is a shit but at least some kind of composition tool. Some way to have resource of various types associated to some top level idea.

Very very little else seems to bring this basic sense to Kubernetes. Metacontroller kind of could do that. Crossplane's whole business is this, but it's been infra-specialized: but the Crossplane v2.0 release is trying to be much more generally useful. https://docs.crossplane.io/v2.0-preview/whats-new/ . Would love other examples of what does composition in Kube.

Re: Broadcom to discontinue free Bitnami Helm charts

#73

Earlier quoted context omitted.

I’ve never used Helm charts. I learned K8S in a shop in which kustomize is the standard and helm is a permitted exception to the standard, but I just never felt any reason to learn helm. Am I missing out? Sometimes the limitations of kustomize annoy me, but we find ways to live with them

Would you like to count the number of spaces that various items in your manifests are indented and then pass that as an argument to a structure-unaware text file templating engine? Would you like to discover your inevitable yaml file templating errors after submitting those manifests to the cluster? Then yes, you are really missing out!

I really, really, wish we could move away from yaml for tools like this.

Re: Broadcom to discontinue free Bitnami Helm charts

#74

This is going to cause some disruptions. What are the alternatives out there to bitnami charts?

https://artifacthub.io/

I don't know why but Artifact Hub never shows up in Google search when you search for "web site with helm charts". Hopefully this gives it a boost.

Re: Broadcom to discontinue free Bitnami Helm charts

#75

Maybe this will finally break me of my habit of using helm charts, period.

I suggest checking out Anemos (https://github.com/ohayocorp/anemos), the new boy in the town. It is an open source single-binary tool written in Go and allows you to use JavaScript/TypeScript to define your manifests using templates, object oriented approach, and YAML node manipulation.

You can read a comparison with Helm here: https://www.ohayocorp.com/anemos/docs/comparison/helm

P.S. I am the author of the tool.

Re: Broadcom to discontinue free Bitnami Helm charts

#77

Hi, former cofounder of Bitnami here. I left VMware quite a while ago, so not involved with this. The technical team at Bitnami is still top notch and great people. I am quite baffled at this business decision.

nobody familiar with broadcom or how they are run should be even remotely surprised by this decision

Re: Broadcom to discontinue free Bitnami Helm charts

#78
post #33

This announcement is a little hard to read. They make it seem that the current images under docker.io/bitnami/* get deleted on August 28? But individual chart READMEs seem to say that images will move during a period starting on August 28 and ending two weeks later? But looking at https://hub.docker.com/u/bitnamilegacy images have been copied already? From ticket https://github.com/bitnami/charts/issues/35164 : > Now…

> What are users expected to do exactly? From the bottom of the post I know what they are hoping users will do: > Suppose your deployed Helm chart is failing to pull images from docker.io/bitnami. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates. They don't want to give instructions that are too helpful. They want…

Looks like it's $5k/month, minimum 12 months for "secure" images.

https://aws.amazon.com/marketplace/pp/prodview-pwqgz3mnvxvok...

You can always follow the "contact sales" form and see if they give you a higher or lower number than that.

Re: Broadcom to discontinue free Bitnami Helm charts

#79
The removal (or moving) of the Bitnami images from Docker Hub is going to break a ton of systems that depend on them. I helped set up https://www.stablebuild.com/ some years ago to counter these types of issues, it provides (among other things) a transparent cache to Docker Hub which automatically caches image tags and makes them immutable - underlying tag might be deleted or modified, but you’ll get the exact same original image back.

Re: Broadcom to discontinue free Bitnami Helm charts

#80

Hi, former cofounder of Bitnami here. I left VMware quite a while ago, so not involved with this. The technical team at Bitnami is still top notch and great people. I am quite baffled at this business decision.

Is there a company more "Take what you can, give nothing back" than Broadcom? Probably not. Broadcom's continued ability to perform well while only serving ever more upmarket areas, & cutting everyone else loose (& generally giving no figs) is fantastically impressive.

Broadcom is just private equity buying products to bleed dry. Nobody thinks VMware is the future, but the folks that use it are enterprises with deep pockets who are slow and reluctant to change so you can multiply the price by big numbers and get paid big while your dying acquired product meets its end.
Post reply on HN