You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
registry.opensource.zalan.do/acid/postgres-operator:v1.9.0
AWS K8s
yes
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: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
andCLONE_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.
The text was updated successfully, but these errors were encountered: