Open FactorT opened 2 years ago
You can indeed add the annotation zalando-postgres-operator-rolling-update-required: true
to the pods and the operator will discover it on next sync and think it has to do a rolling update.
Thank you very much @FxKu! This workaround sounds good. But is there a way to force operator run sync operation early? For example via send a request to service postgres-operator.
Only by deleting the operator pod you can force a sync of all clusters.
Thank you very much @FxKu for your answers! Could you give me advise please.
I want to try make a PR with switchover functionality via operator. How do you think is it possible to realise it with the next approach?
You can indeed add the annotation
zalando-postgres-operator-rolling-update-required: true
to the pods and the operator will discover it on next sync and think it has to do a rolling update.
Is it recommended to remove annotation after rollout?
I noticed that when the annotation is removed, another rollout happens. I also saw that regardless of the true
or false
value, the rollout happens, is this expected?
Please, answer some short questions which should help us to understand your problem / question better?
Does the operator support manual swithover? I know that I can enter in pod and run switchover via patronictl. But it may be convenient and useful to be able to do a switchover using an operator, for example, through an endpoint annotation.