Multi region setup on EKS - Question

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
  ghcr.io/zalando/spilo-15:2.1-p9
• Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
  AWS EKS
• Are you running Postgres Operator in production? [yes | no]
  YES
• Type of issue? [Bug report, question, feature request, etc.]
  Question In our current setup Postgres operator and related data pods ( databases) running in AWS east region. Some of our customers are in Europe region and they are requesting to have this setup in EU region. Is there any inbuilt provision which can be used to spin off new clusters in new region. What is the optimal way to shift some of our workloads ( we call it data pods of databases ) from current region to EU region**

Start by reviewing the Postgres Operator and Spilo deployment setup described for AWS EKS, focusing on how clusters and database data pods are deployed across regions. Done means providing a confirmed, project-specific answer about multi-region provisioning and the recommended way to move workloads to the EU region; the issue names no files or tests.