You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Given multiple nodepools, in order to ensure that ONLY the runners are scheduled to a specific nodepool, it will have to be tainted with preferably a NO_SCHEDULE effect.
For kube-scheduler to be able to schedule the runner workloads to that nodepool, the runners will need to have tolerations to the taints.
This is frustrating for us at the moment since our nodepools are being shared by all the workloads in the cluster.
Describe the solution you'd like
Add tolerations to the workloads/deployments so that they can be scheduled on a tainted node(pool).
Describe alternatives you've considered
I've considered using nodeAffinity. But this does not prevent other workloads from being scheduled to the runner nodepools. Which in turn introduces a competition for resources.
Additional context
N/A
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Given multiple nodepools, in order to ensure that ONLY the runners are scheduled to a specific nodepool, it will have to be tainted with preferably a NO_SCHEDULE effect.
For kube-scheduler to be able to schedule the runner workloads to that nodepool, the runners will need to have tolerations to the taints.
This is frustrating for us at the moment since our nodepools are being shared by all the workloads in the cluster.
Describe the solution you'd like
tolerations
to the workloads/deployments so that they can be scheduled on a tainted node(pool).Describe alternatives you've considered
nodeAffinity
. But this does not prevent other workloads from being scheduled to the runner nodepools. Which in turn introduces a competition for resources.Additional context
The text was updated successfully, but these errors were encountered: