argocd-operator VS postgres-operator

The deploy folder is in the releases. So if you're installing 0.0.5, you'd go to https://github.com/argoproj-labs/argocd-operator/tree/v0.0.15/deploy

Another installation variant is the additional ArgoCD operator. This allows the actual ArgoCD components to be installed and configured via CRD. It is not documented how you can configure ArgoCD yourself via GitOps. This is conceivable, for example, using the ArgoCD operator. It remains to be determined whether this will work reliably and, above all, whether it supports continued operation via GitOps in the event of an error.

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