charts

Compare to bitnami: https://github.com/bitnami/charts/issues/35164 Recently switched from bitnami to minio here, with plenty heads up & they scheduled brown outs etc, along with legacy images to fallback on for users who don't get informed by anything until image gone

This is covered in the official GitHub issue: https://github.com/bitnami/charts/issues/35164 Q: What will happen to the existing OCI Helm charts? A: The already packaged Helm charts will remain available at docker.io/bitnamicharts as OCI artifacts, but they will no longer receive updates. Deploying these charts will not work out-of-the-box unless you override the bundled images with valid ones. *except for the BSI images included in the free community-tier subset.

They write in the press release, that the sources remain under Apache 2 license, they just stop distributing prebuilt images for free. Edit: As I see it's true. Source code for OCI images: https://github.com/bitnami/containers/tree/main/bitnami Charts: https://github.com/bitnami/charts/tree/main/bitnami

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 – August 28th, 2025: Plan your migration: Update CI/CD pipelines, Helm repos, and image references > August 28th, 2025: Legacy assets are archived in the Bitnami Legacy repository. From README https://github.com/bitnami/charts/blob/4973fd08dd7e95398ddcc...: > Starting August 28th, over two weeks, all existing container images, including older or versioned tags (e.g., 2.50.0, 10.6), will be migrated from the public catalog (doc

I share your dislike of Helm, but FYI there are schemas for values, see for example https://github.com/bitnami/charts/blob/main/bitnami/postgres... and docs https://helm.sh/docs/topics/charts/#schema-files

K3s installs super fast. Writing your first yaml or two is scary & seems intimidating at first . But after that, everything is cut from the same cloth. Its an escape from the long dark age of every sysadmin forever cooking up whatever whimsy sort of served them at the time, escape from each service having very different management practices around it. And there's no other community anywhere like Kubernetes. Unbelievably many very good quality very smart helm charts out there, such as https://github.com/bitnami/charts/tree/main/bitnami just ready to go. Really sweet home-ops setups like https://github.com/onedr0p/home-ops that show that once you have a platform under foot, adding more services is really easy, showing an amazing range of home-ops things you might be interested in. > Last thing I need is Kubernetes at home Last thing we need

I run a few PostgreSQL instances in containers (Kubernetes via Bitnami Helm chart). I know running stateful databases is generally not best practice but for development/homelab and tinkering works great. Bitnami PostgreSQL Helm chart - https://github.com/bitnami/charts/tree/main/bitnami/postgres...

Hi there, I've been working on a Kubernetes Operator to deploy and manage Valkey Cluster (https://valkey.io). I was unsatisfied with the existing options available, and felt that it didn't hurt to create a new one. I know a lot of folks are going to make the case that the Bitnami helm chart (https://github.com/bitnami/charts/tree/main/bitnami/valkey-c...) is good enough, or just use a cloud provider option is ideal. And for some use cases that makes sense, but for a lot of other use cases, especially testing, and multi-tenant SaaS offerings I think an Operator provides a reliable mechanism to satisfy the middle ground.

> Why are the storage and networking implementations "out of tree" (CNI / CSI)? Given the above question, why is there explicit support for Cloud providers? eg: LoadBalancer supports AWS/GCP/Azure/.. Kubernetes has been pruning out vendor-specific code for a while now, moving it out of tree. The upcoming 1.31 release will drop a lot of existing, already deprecated support for AWS & others from Kubernetes proper. https://github.com/kubernetes/enhancements/blob/master/keps/... There's some plan to make this non-dosruptive to users but I haven followed it closely (I don't use these providers anyhow). > Why are we generating a structured language (YAML), with a computer, by manually adding spaces to make the syntax valid? There should be no intermediate text-template representation like this one. Helm is indeed a wild world. It's also worth n

If you can manage it yourself, I advise using the Bitnami PostGreSQL on top of Kubernetes. Using this, you will have a more solid installation than what is offered by many local cloud providers. Kubernetes can be scary, but it's not too hard to maintain if you use a simple Kubernetes distribution like K3S. https://bitnami.com/stack/postgresql/helm https://github.com/bitnami/charts/tree/master/bitnami/postgr... https://k3s.io - Otherwise you can definitely find a local provider offering managed PostGreSQL databases. Just for the big ones in Europe: https://www.scaleway.com/en/database/ https://www.ovhcloud.com/en-ie/public-cloud/databases/ https://www.hetzner.com/webhosting

I'm hoping these kinds of policies continue to be phased out. The Kubernetes world has changed a lot in the past few years in ways that make databases-in-k8s more appealing. Such as: - Kubernetes "eating the world", meaning some teams may not even have good options for databases outside k8s (particularly onprem). - Infrastructure-as-code being more prevalent. Since you already have to use k8s manifests for the rest of your app, adding another IaC tool to set up RDS may be undesirable. - The rise of microservices, where companies may have hundreds of services that need their own separate data stores (many which don't see high enough traffic to justify the cost of a managed database service). - Excellent options like the bitnami helm charts: https://github.com/bitnami/charts or apparently Vitess (haven't used it myself): https://vitess.io/