fix: add node affinity based on resource label #152
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By design, the resource.labelselector should be used to add node affinity to make sure workload run in the provisioned nodes.
The workload label selector should use a different one. This makes it possible for two workspaces to share the same nodes.
Also, remove pod anti-affinity rule which is unnecessary. The Pod GPU request makes sure the GPU node is not overcommitted.