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

[FEATURE] Add tolerations to tainted nodes #26

Open
emmanuelstroem opened this issue Sep 21, 2023 · 0 comments
Open

[FEATURE] Add tolerations to tainted nodes #26

emmanuelstroem opened this issue Sep 21, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@emmanuelstroem
Copy link
Contributor

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
@emmanuelstroem emmanuelstroem added the enhancement New feature or request label Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant