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? e.g. ghcr.io/zalando/postgres-operator:v1.13.0
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, feature request]
Hello,
First of all, thanks for your great work.
I'd like to know if there is a way to manually trigger a sync operation for a specific pg cluster? For example it would be helpful if I could call a REST Api method with curl to initiate a manual sync for a specific cluster.
Why is this a requirement?
I update the password in a secret for a regular application db user and then wait until the next cycle (can take up to 30m) until the new password propagates to database. During this time the password in the secret and the actual password in the database don't match causing application issues. It would be helpful to be able to initiate a secret sync for a specific cluster manually.
The text was updated successfully, but these errors were encountered:
Hello,
First of all, thanks for your great work.
I'd like to know if there is a way to manually trigger a sync operation for a specific pg cluster? For example it would be helpful if I could call a REST Api method with curl to initiate a manual sync for a specific cluster.
Why is this a requirement?
I update the password in a secret for a regular application db user and then wait until the next cycle (can take up to 30m) until the new password propagates to database. During this time the password in the secret and the actual password in the database don't match causing application issues. It would be helpful to be able to initiate a secret sync for a specific cluster manually.
The text was updated successfully, but these errors were encountered: