zalando / zalando/postgres-operator
Move psql cluster to another aws account
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.2k
- Forks
- 1.1k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 3
Description
- 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the clone instructions, issue 2394, and the mentioned clone_with_wale.py entry point. Then inspect the postgres-operator ConfigMap settings for IRSA and cross-account cloning. Done means documenting whether moving a PostgreSQL cluster between AWS accounts is supported and which S3 and IAM configuration is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, postgresql
- Domain
- cloud, databases, devops
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100