Please, answer some short questions which should help us to understand your problem / question better?
Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.9.2
Where do you run it - cloud or metal? Kubernetes or OpenShift? [Bare Metal K8s]
Are you running Postgres Operator in production? Yes
Type of issue? [Question]
We run Single Node and Multi Node CLusters and recently moved storage to ZFS. On our Single Node Clusters, we have 2 mirrored zfs pools, each are mapped to a different openebs provider Storage Class.
We would like to be able to put the master on one storage class, and replicas on another, to keep the data physically separated, and let us use zfs to snapshot the replica only
Is this possible? So far I can not see a way to achieve this, but likely I'm missing something obvious
The storage class you can define in the volume section of the Postgres manifest will be used for all PVCs of the database cluster. We do not support any distinction between primary and replicas.
Please, answer some short questions which should help us to understand your problem / question better?
We run Single Node and Multi Node CLusters and recently moved storage to ZFS. On our Single Node Clusters, we have 2 mirrored zfs pools, each are mapped to a different openebs provider Storage Class.
We would like to be able to put the master on one storage class, and replicas on another, to keep the data physically separated, and let us use zfs to snapshot the replica only
Is this possible? So far I can not see a way to achieve this, but likely I'm missing something obvious
Many thanks in advance