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

Method for Manually Triggering Sync for a specific Cluster #2835

Open
emrahbecer opened this issue Jan 7, 2025 · 0 comments
Open

Method for Manually Triggering Sync for a specific Cluster #2835

emrahbecer opened this issue Jan 7, 2025 · 0 comments

Comments

@emrahbecer
Copy link

  • 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.

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