-
Notifications
You must be signed in to change notification settings - Fork 54
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
Add node selector strategy for exclusive job placement per topology #311
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: danielvegamyhre The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
16d5417
to
6ab0768
Compare
@@ -0,0 +1,104 @@ | |||
#!/usr/bin/python3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some comment on how this script can be used would be good and the args they need to pass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
added. let me know if it is too detailed, or if perhaps i should include a concrete example use case?
/lgtm |
a15b1a5
to
7ba3f58
Compare
/lgtm |
Fixes #312
Add node selector strategy for exclusive job placement per topology.
NodeSelectorStrategyKey is an annotation that acts as a flag, the value does not matter. If set, the JobSet controller will automatically inject nodeSelectors for the JobSetNameKey label to ensure exclusive job placement per topology, instead of injecting pod affinity/anti-affinites for this. The user must add the JobSet name node label to the desired topologies separately.
I manually verified the python script works on a test cluster.