Hello
As seeing the need to make a replication possible on the database side I thought about throwing this idea here ( if not already thought ).
I am deploying pulp via the operator to a k8s cluster and it would be nice to have the replication possible via the pulp config file as for api/worker/web/content pod available.
Why: To have some sort of loadbalacing, keep the same set of data replicated to each of the databases in case something goes wrong in one of them.
Hi @AJJA,
Yep, we agree that it would be nice if pulp-operator could manage/deploy a cluster of postgres (and/or redis). This is something we discussed in the past, but decided to not implement because it would be very complex and there are already operators dedicated to postgres cluster management. So, for deployments where high availability is expected, we recommend configuring pulp-operator to use an “external” (not deployed by pulp-operator) database instance: Configure Pulp Database - Pulp Project.
Here are some postgres operators we found in operatorhub:
https://operatorhub.io/operator/cloudnative-pg
https://operatorhub.io/operator/postgresql
https://operatorhub.io/operator/postgres-operator