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

Support node readiness labels #509

Closed
liger1978 opened this issue Mar 8, 2022 · 3 comments · Fixed by #541
Closed

Support node readiness labels #509

liger1978 opened this issue Mar 8, 2022 · 3 comments · Fixed by #541
Milestone

Comments

@liger1978
Copy link

The Zalando PostgreSQL Operator depends on node readiness labels to schedule pods on nodes. To trigger a failover of the "leader" role in the PostgreSQL Patroni HA cluster from one pod to another in the event of a node reboot, a label must be updated on the node before it is cordoned and drained. The label must be updated once more after the node is rebooted and uncordened.

Would you accept a PR to optionally update node readiness labels before and after the reboot process?

@evrardjp
Copy link
Collaborator

evrardjp commented Mar 8, 2022

It makes sense to me.

@liger1978
Copy link
Author

Please review/merge PR #541 that adds this enhancement. I have built and tested kured from PR #541. It works fine.

@liger1978
Copy link
Author

@ckotzbauer @evrardjp

@ckotzbauer ckotzbauer added this to the 1.10.0 milestone May 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants