-
Notifications
You must be signed in to change notification settings - Fork 408
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
[BUG] pool-coordinator isn't rescheduled when its node disconnects from others #1212
Labels
kind/bug
kind/bug
Comments
I think we can remove such toleration from pool-coordinator. Would you like to submit a pr? @AndyEWang |
@Congrool Ok, I will submit one if there is no special case to bind pool-coordinator to a node. |
AndyEWang
added a commit
to AndyEWang/openyurt
that referenced
this issue
Feb 9, 2023
openyurt-bot
pushed a commit
that referenced
this issue
Feb 10, 2023
github-actions bot
pushed a commit
that referenced
this issue
Feb 17, 2023
(cherry picked from commit 08d8d74)
openyurt-bot
pushed a commit
that referenced
this issue
Feb 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
when the node disconnects from all nodes except itself, pool-coordinator in this node cannot be evicted.
What you expected to happen:
pool-coordinator should be rescheduled into a healthy node.
How to reproduce it (as minimally and precisely as possible):
just shutdown the node where pool-coordinator is located and the Pod of pool-coordinator won't be rescheduled.
Anything else we need to know?:
found that charts/openyurt/templates/pool-coordinator.yaml is configured with
Environment:
kubectl version
): 1.22/kind bug
The text was updated successfully, but these errors were encountered: