-
Notifications
You must be signed in to change notification settings - Fork 114
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
Change logic to prevent device-plugin daemonset spec change #740
Change logic to prevent device-plugin daemonset spec change #740
Conversation
Thanks for your PR,
To skip the vendors CIs, Maintainers can use one of:
|
hi @AMacedoP , the problem you're describing has probably already been solved by:
That said, I'm not against the proposed changes, as they make the code clearer and more resilient. |
@zeeke yes, that PR also solves my problem. How do you want to proceed with this PR? If you want I can resolve the failed test cases and merge it. |
Please, fix the unit test and wait for the other community member's feedback. @adrianchiris , @SchSeba WDYT? |
Instead of adding a NodeSelectorRequirement per NodePolicy we add all the NodeSelectors to a single NodeSelectorRequirent so they can all be sorted. This will prevent that the daemonset's node selector changes when there are multiple NodePolicies applied. Signed-off-by: Alejandro Macedo <[email protected]>
05702e7
to
79ff9d2
Compare
Hi @AMacedoP, Thanks for the PR! I think that is cleaner let me know what you think |
@SchSeba that looks like a good solution. In that case what should we do with this PR? |
Instead of adding a NodeSelectorRequirement per NodePolicy we add all the NodeSelectors to a single NodeSelectorRequirent so they can all be sorted. This will prevent that the daemonset's node selector changes when there are multiple NodePolicies applied.