@Randy Alejo I’m not that deeply involved in it yet. So far, I’ve mostly just done reviews or administrative stuff. I’m currently getting up to speed myself because I want/need to make some adjustments for OKD. 😅🫣

Hey folks I'm working on the openvoxdb helm chart and I was trying to align it with the monolith chart I sent earlier

I noticed that for its PostgreSQL instance its using a bitnami postgresql chart using bitnami legacy

I know there's been issues with bitnami in the past paywalling their stuff, I was wondering if for the new chart you guys would prefer I stick to using bitnami or if I should implement and configure PostgreSQL directly in the openvoxdb chart using the official postgres image

or alternatively I can use a different subchart like HelmForge or CloudPirates. What do you guys recommend?

I'm in favor of switching away. Like, I get that maintaining software is work, and open source work should get paid (I mean, obviously, look who's talking, look where I am lol).

But charging for what is the equivalent of a makefile is beyond me.

(I get there's a bit more to bitnami than that, but still)

I haven't experimented with the alternatives, so the easy answer would be to aim for upstream and use the official postgres image. But I've heard decent things about helmforge, I just can't personally vet for them.

The official Postgres image works well. I've swapped it for Bitnami in a few places.

Oh and would you look at that!

I'll have to take a look at 213 and see about moving things forward, but first I'm headed out for an appointment. Exciting times, though.

For the PostgreSQL thingy, I'm trying to work on github.com/OpenVoxProject/container-openvoxdb-postgres. I've heard that it's preferable to have a fully prepared image instead of cobbling something together on the fly.

It doesn’t feel right to reinvent the wheel here and ship our own container image, in my opinion

Plus it’s another thing to maintain, with its own separate release cycle, etc…

Honestly I’d just bundle the most basic image and sub-chart we can find that’s actually maintained, and point people at a proper PostgreSQL operator like CloudNativePG or Zalando Postgres Operator for actual production deployments

hmm okay. which chart is it then? do we have a direction here? or is everything unclear? because i want to push forwards here. a customer of mine has some money so do development here. just need a direction. 🙂

Honestly I’d just bundle the most basic image and sub-chart we can find that’s actually maintained, and point people at a proper PostgreSQL operator like CloudNativePG or Zalando Postgres Operator for actual production deployments

oh, oversaw the last line... okay, then i see how to incorporate this into my work for the customer

I would vote for CloudPirates

postgres

(github.com/CloudPirates-io/helm-charts) is the closest drop-in for what we have. Apache-2.0, actively released, official

<http://docker.io/postgres|docker.io/postgres>

image pinned by digest, and it has the same hooks the chart already uses:

initdb.scriptsConfigMap

for our pg_trgm/pgcrypto ConfigMap and

auth.existingSecret

/

customUser

for the credentials.

Of course the swap isn't just a simple dependency bump, Bitnami 12.1.11 is PG 15 in /bitnami/postgresql/data and CloudPirates is PG 18 in /var/lib/postgresql, so existing installs need a dump/restore or pg_upgrade path and the chart keeps the PVC on uninstall. My #53 fixes the default install's "database openvoxdb does not exist" and its helper reads the Bitnami value keys, so it will need updating to whatever replaces it.

Seconding (thirding?) against reinventing the wheel. Postgres also publishes its own images and minimal helm chart.

for my implementation based off what I read here I decided to replace Bitnami's chart with HelmForge's chart.

I was choosing between HelmForge and CloudPirates. Cloudpirates is simpler and HelmForge seemed more complete with features I've found useful (like backups and stuff). Both use the official postgres image

helmforge.dev it seems to present itself as Bitnami's replacement

The open-source alternative to Bitnami. Official upstream images, built-in S3 backups, sane security defaults, and day-two operations — Apache-2.0 licensed, free forever.

I'm also cool with Cloudpirates, i just chose HelmForge because i liked built-in S3 backups and commitment to staying free

on that note I made a PR for the openvoxdb helm chart here: github.com/OpenVoxProject/helm-charts/pull/4 let me know if I need to make any changes, this is my first time contributing to open source software

#53 for which repo?

this will build VoxBox with openvox9 and openvox8, 9 will be the default github.com/voxpupuli/container-voxbox/pull/366