-
Notifications
You must be signed in to change notification settings - Fork 99
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
fix: allow jobs and sts to have the same tolerations and nodeselectors #306
Conversation
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.
Looks great, thanks for getting this PR up so quickly! Also thanks for creating _statefulset-helpers.tpl
, I think this approach to organizing named templates will help over time.
I've tested this change out and it works as intended. My only feedback is that the new named templates are an either/or approach when maybe they could allow an aggregate for both nodeSelector and tolerations. In other words. If values are found in both statefulset and the top-level parameter then both are used. This isn't a blocker though, we can talk about it and improve the implementation over time if we agree.
This would break if the user wanted only the sts to be on one set of nodes, and all the ancillary work to run on another, ie. Jobs run on |
8e96f6e
to
4fa359f
Compare
I'm working on a PR to ensure that the jobs and statefulset pods use distinct labels so as not to have jobs match the statefulset selector. That PR needs merged first. |
@alejandroEsc Can you add test that uses |
I know i can use the labels on kind workers. What do you mean by "use annotations"? |
I wrongly write |
610df7d
to
1037201
Compare
1037201
to
e66446b
Compare
e66446b
to
129c4a9
Compare
…e/issues/305 fix: allow jobs and sts to have the same tolerations and nodeselectors
Tested this locally:
Fixes #305