-
Notifications
You must be signed in to change notification settings - Fork 445
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] session config k8s_coordinator_pod_node_selector Not effective #3476
Labels
Comments
Hi, @JackyYangPassion. Thanks for the report. Could you please provide the full error log? Thanks. |
Thanks for your reply @dashanji
|
@JackyYangPassion Thanks, we try to reproduce the bug. |
/cc @yecol @sighingnow, this issus/pr has had no activity for a long time, please help to review the status and assign people to work on it. |
siyuan0322
pushed a commit
that referenced
this issue
Jun 11, 2024
…3477) ## What do these changes do? As titled. During test, I find not all pods are scheduled to the same node. ```yaml NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES coordinator-ozgjbb-6c57549cf7-hhwqt 1/1 Running 0 4m2s 10.244.1.85 kind-worker <none> <none> gs-engine-ozgjbb-0 3/3 Running 0 3m58s 10.244.1.86 kind-worker <none> <none> gs-engine-ozgjbb-1 3/3 Running 0 114s 10.244.1.87 kind-worker <none> <none> gs-engine-ozgjbb-2 3/3 Running 0 108s 10.244.1.88 kind-worker <none> <none> gs-engine-ozgjbb-ozgjbb-vineyard-etcd-0 1/1 Running 0 3m58s 10.244.3.71 kind-worker2 <none> <none> gs-interactive-frontend-ozgjbb-8d996bc8b-ctn6x 1/1 Running 0 3m58s 10.244.3.72 kind-worker2 <none> <none> ``` We should support to add the node selector to the frontend and vineyard etcd. ## Related issue number Fixes #3476 --------- Signed-off-by: Ye Cao <caoye.cao@alibaba-inc.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
add label for k8s worker
create session
error log
The text was updated successfully, but these errors were encountered: