Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Broadcom to discontinue free Bitnami Helm charts

github.com

Post reply on HN
Print view View original

131–140 of 142 posts

Re: Broadcom to discontinue free Bitnami Helm charts

#131

Post by NewJazz »

mdaniel wrote: post #129
NewJazz wrote: post #127

Earlier quoted context omitted.

That is when you are writing the values when using the chart though, right? Yeah that's not too hard. I was talking about the go templates that make up the actual chart. Ensuring they only use string values for annotations for example seems like a hard problem to solve. Even just showing the type and description from the schema seems nontrivial.

I don't exactly follow which part you're talking about, but yes JetBrains propagates the type and description from the JSON Schema into the golang templates inside the manifest files, same as it does with any type completion. They are reflected as their JSON Schema types, not golang's types, which I could imagine is potentially confusing to someone used to golang's view of the world but is for sure considerably bette…

Oh, OK. I didn't realize it made them visible in the golang templates.

Re: Broadcom to discontinue free Bitnami Helm charts

#132

Post by kkapelon »

0xbadcafebee wrote: post #113
bo0tzz wrote: post #86

Earlier quoted context omitted.

> zero to fully running (...) in 5 seconds by just running helm install Realistically, a plain helm install without any values rarely if ever gives you the deployment you need, so you have to study the chart anyways. > rollback on failure This is hardly unique to helm. > history metadata without (...) some external system In 2025 you should probably be using gitops anyways, in which case the git repo is your history.

> a plain helm install without any values rarely if ever gives you the deployment you need works for me most of the time > This is hardly unique to helm. So what? The guy was asking what is nice about Helm vs Kustomize. Does Kustomize have rollbacks? > In 2025 you should probably be using gitops Gitops is literally just "hey I have some configs in Git and I run some command based on a checkout", i.e. infrastructure a…

> Gitops is literally just...

Please check https://opengitops.dev/

Re: Broadcom to discontinue free Bitnami Helm charts

#133

Post by okanat »

pjmlp wrote: post #130
okanat wrote: post #121

Earlier quoted context omitted.

Java has a much stronger open source community with lots of corporate players. If Oracle tried to close the doors on it, everybody can pivot away in much shorter time than Vmware.

Where were all those players when Google torpedoed Sun? The large majority of work done in OpenJDK is by Oracle employees. Had it been for most of those players, Java 6 would have been the last version.

I don't exactly get what you mean by "Google torpedoed Sun".

Corporate players came into play after Oracle acquired Sun. The fear that Oracle would do the same as LibreOffice pushed players like IBM to have their own Java distributions.

Of course Oracle having more support for OpenJDK is not surprising. However, the open nature and existing players already make it easier to fork / replace Java compared to Vmware.

Re: Broadcom to discontinue free Bitnami Helm charts

#134

Post by pjmlp »

okanat wrote: post #133
pjmlp wrote: post #130

Earlier quoted context omitted.

Where were all those players when Google torpedoed Sun? The large majority of work done in OpenJDK is by Oracle employees. Had it been for most of those players, Java 6 would have been the last version.

I don't exactly get what you mean by "Google torpedoed Sun". Corporate players came into play after Oracle acquired Sun. The fear that Oracle would do the same as LibreOffice pushed players like IBM to have their own Java distributions. Of course Oracle having more support for OpenJDK is not surprising. However, the open nature and existing players already make it easier to fork / replace Java compared to Vmware.

Sun did not sue Google because they already lacked the money to do so.

What Google did with Android, it is hardly any different from Microsoft with J++, only that there the courts had another outcome.

Android with a Java subset and Kotlin, is hardly any different outcome than .NET with C#.

Corporate players came in, after money was available again, after the acquisition.

"James Gosling Triangulation's Interview on Google vs. Sun"

https://www.youtube.com/watch?v=ZYw3X4RZv6Y&t=3462s

"James Gosling on Android and Java"

https://www.youtube.com/watch?v=IT__Nrr3PNI&t=6245s

If Google actually cared about Java, they missed their opportunity to acquire Sun, own Java, do whatever they felt like doing with it for Android, and the rest of the industry, and best of all, they would never had to bother with any lawsuit.

Given how much the so called existing players contributed to save Java while Sun was going under, that is whishful thinking.

Re: Broadcom to discontinue free Bitnami Helm charts

#135

Post by tranatyl »

carrodher wrote: post #31
sseveran wrote: post #14

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

The source code for Bitnami containers and Helm charts remains publicly available on GitHub and continues to be licensed under Apache 2. What’s changing is that Bitnami will no longer publish the full catalog of container images to DockerHub. If you need any image, you can still build/package it yourself from the open-source GitHub repositories.

What about the bitnami:minideb base image? Or the stacksmith files necessary to build certain images? Without access to these resources, it will not be possible to rebuild the images, will it?

Re: Broadcom to discontinue free Bitnami Helm charts

#136

Post by mdaniel »

tranatyl wrote: post #135
carrodher wrote: post #31

Earlier quoted context omitted.

The source code for Bitnami containers and Helm charts remains publicly available on GitHub and continues to be licensed under Apache 2. What’s changing is that Bitnami will no longer publish the full catalog of container images to DockerHub. If you need any image, you can still build/package it yourself from the open-source GitHub repositories.

What about the bitnami:minideb base image? Or the stacksmith files necessary to build certain images? Without access to these resources, it will not be possible to rebuild the images, will it?

Seems to be Apache 2 https://github.com/bitnami/minideb/blob/1694284885fecfb852b0... and it has GHA (although I didn't verify that it could plausibly run outside of their GH org) https://github.com/bitnami/minideb/blob/1694284885fecfb852b0...

Re: Broadcom to discontinue free Bitnami Helm charts

#137

Post by carrodher »

tranatyl wrote: post #135
carrodher wrote: post #31

Earlier quoted context omitted.

The source code for Bitnami containers and Helm charts remains publicly available on GitHub and continues to be licensed under Apache 2. What’s changing is that Bitnami will no longer publish the full catalog of container images to DockerHub. If you need any image, you can still build/package it yourself from the open-source GitHub repositories.

What about the bitnami:minideb base image? Or the stacksmith files necessary to build certain images? Without access to these resources, it will not be possible to rebuild the images, will it?

Projects like Sealed Secrets and minideb remain unaffected by these changes. Container images for both projects will continue to be released on Docker Hub (docker.io/bitnami) as usual, without any modifications.

The source code will continue to be available for containers, allowing you to build them from source and future versions as well. The Stacksmith tarballs will also remain available.

The planned action is to stop providing the already built containers on Docker Hub.

Re: Broadcom to discontinue free Bitnami Helm charts

#138

Post by hbogert »

dpkirchner wrote: post #61
cbzbc wrote: post #28

Earlier quoted context omitted.

What are you planning on moving to ?

I'm using either opentofu(terraform) or plain yaml. I'm not a huge fan of HCL but at least it is structured and easily manipulated without worrying about whitespace.

easily manipulated? How?

Re: Broadcom to discontinue free Bitnami Helm charts

#139

Post by thayne »

stackskipton wrote: post #109
9dev wrote: post #96

Earlier quoted context omitted.

I never understood why people didn’t serialize from JSON if they run a transformation step on the YAML anyway. Read JSON, alter in your favorite language, dump YAML as the last step, deploy. Instant prevention of a lot of sadness. Yet somehow, all we have is YAML templating?

Kubectl will handle JSON without converting it to YAML. So if you are doing this, then just do kubectl apply -f deployment.json

So why doesn't helm output to json instead of yaml, and avoid all the problems with significant whitespace?

Re: Broadcom to discontinue free Bitnami Helm charts

#140

Post by imglorp »

dpkirchner wrote: post #16

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

Most on this thread are viewing helm from a user perspective: "I want to install X and I can use somebody's chart for it or I can use another tool."

There is another category of users who want a way to mange multiple vendor offerings in a consistent manner into their clusters. If they're all packaged with Helm, the user can have standard process and tooling to do that. It's done for K8s apps what containers did for executables.

Is it great? No, see the grief and pain in sibling threads. Are there alternatives? Sure. But Helm is sort of a standard at this point, warts and all.

I work for a vendor that sells to the second category usually, my chart has some 45 images with some intricate hooks for install and upgrade, subcharts, multiple namespaces, etc. You'd be hard pressed to repackage our stuff for every release we give you.

Post reply on HN