🐛 fix: target vllm-d deploy runners with openshift label#4017
🐛 fix: target vllm-d deploy runners with openshift label#4017clubanderson merged 1 commit intomainfrom
Conversation
…cks from stealing deploy jobs The deploy-vllm-d job used `runs-on: [self-hosted, kc]` which matched both vllm-d (npmh7) and scooter-cks (dmcrj) runners. When GitHub assigned the job to a scooter-cks runner, it failed because those runners lack RBAC and target the wrong cluster. Adding the `openshift` label narrows the selector to only vllm-d runners. Signed-off-by: Andrew Anderson <andy@clubanderson.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole canceled.
|
|
👋 Hey @clubanderson — thanks for opening this PR!
This is an automated message. |
|
Thank you for your contribution! Your PR has been merged. Check out what's new:
Stay connected: Slack #kubestellar-dev | Multi-Cluster Survey |
There was a problem hiding this comment.
Pull request overview
This PR fixes intermittent failures in the deploy-vllm-d GitHub Actions job by narrowing the self-hosted runner selection so the job only lands on the intended OpenShift-backed vllm-d runner pool.
Changes:
- Update
deploy-vllm-drunner selector to include theopenshiftlabel ([self-hosted, kc, openshift]) to avoid accidentally matching scooter-cks runners.
Summary
deploy-vllm-djob usedruns-on: [self-hosted, kc]which matched both vllm-d and scooter-cks runnersopenshiftlabel to the selector →[self-hosted, kc, openshift]— only vllm-d runners have this labelRunner inventory
npmh7(2 pods)self-hosted, kc, openshiftdmcrj(2 pods)self-hosted, kc, cks, scootertsspd(2 pods)self-hosted, kc-pok, openshiftTest plan
npmh7runner (check runner name in job logs)