operator VS postgres-operator

minio has a k8 operator as well which I use at work: https://github.com/minio/operator

So far I have seen some minio documentation (1, 2, ) about how to add the certificates correctly but I haven't been able to set it up correctly :-(

Yesterday, I tried to install MinIO, as I'm looking for a distributed object storage solution for Spark jobs on Kubernetes. I read the docs, went to the Github repo and followed the steps to install it using Helm. Here's what I did :

Thank you! I assume you refer to this operator here, am I right? I will have a look at this, and also at the annotations possibility. Another question: is it deliberate that no Helm install is available?

I found a couple of those Postgres operators, like the movetokube/postgres-operator but I honestly can't tell which of them are any good. Do you have any experience with them? I also would need something for MinIO, since I'm able to use Terraform to create databases, buckets and then spin up the app. It's a really comfortable process albeit I do prefer GitOps.

Not everything carries over from Terraform to GitOps but with that said check out this operator that lets you provision an existing postgres database.

On my list is the external postgres operator to provision databases on the external postgres instance, similar to using democratic-csi for providing volumes on the TrueNAS host. https://github.com/movetokube/postgres-operator

Others have mentioned some great operators for managing in-cluster postgres databases, but if you're looking to manage external or previously existing databases: https://github.com/movetokube/postgres-operator

That is my plan, too. I have the External Postgres Server Operator on my list of thing to try out. Does anyone have experience with it already?

Here is an example of an operator that creates databases: https://github.com/movetokube/postgres-operator