Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move psql cluster to another aws account #2587

Open
v-novytskyi opened this issue Mar 18, 2024 · 0 comments
Open

Move psql cluster to another aws account #2587

v-novytskyi opened this issue Mar 18, 2024 · 0 comments

Comments

@v-novytskyi
Copy link

  • Which image of the operator are you using?
    registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
  • Where do you run it - cloud or metal? Kubernetes or OpenShift?
    AWS K8s
  • Are you running Postgres Operator in production?
    yes
  • Type of issue?
    question

In docs i see instructions how to clone, but what about move cluster to another aws account in eks?
What i try?
Copy psql folder to the second account to already exist s3 bucket. Manually created secrets, use clone block with uid|cluster|timestamp. For now i getting error:

trying to bootstrap a new cluster
INFO: Running custom bootstrap script: envdir "/run/etc/wal-e.d/env-clone-test-postgresql" python3 /scripts/clone_with_wale.py --recovery-target-time="***"
INFO: Trying s3://****/15/ for clone

I see an issue which may help me. But i have question, is there any reason which may disserve to other psql clusters in second account? Do i need add CLONE_AWS_ROLE_ARN and CLONE_AWS_WEB_IDENTITY_TOKEN_FILE in postgres-operator configMap?
btw i already use in cm IRSA and don't understand why it not works with clone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant