-
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
deploy: relax Operator node affinity #806
Conversation
Thanks for your PR,
To skip the vendors CIs, Maintainers can use one of:
|
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.
LGTM
nice work!
Pull Request Test Coverage Report for Build 11894643215Details
💛 - Coveralls |
LGTM! |
Hi @EmilienM can you take a quick look on the failed in the ocp lane please |
please take a look on the helm deployment sriov-network-operator/deployment/sriov-network-operator-chart/values.yaml Lines 10 to 24 in aecb4bb
|
a5147b7
to
2afb54d
Compare
2afb54d
to
3261be4
Compare
deploy/operator.yaml
Outdated
preference: | ||
matchExpressions: | ||
- key: "node-role.kubernetes.io/control-plane" | ||
operator: In |
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.
I think here you can use Exist and remove the values
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.
This was copied from
sriov-network-operator/deployment/sriov-network-operator-chart/values.yaml
Lines 11 to 24 in 92fee7b
nodeAffinity: | |
preferredDuringSchedulingIgnoredDuringExecution: | |
- weight: 1 | |
preference: | |
matchExpressions: | |
- key: "node-role.kubernetes.io/master" | |
operator: In | |
values: [""] | |
- weight: 1 | |
preference: | |
matchExpressions: | |
- key: "node-role.kubernetes.io/control-plane" | |
operator: In | |
values: [""] |
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.
I applied your suggestion though.
In the context of Hypershift (Hosted Clusters with OpenShift), where a Nodepool (terminology for a worker Node in HCP) is not a control-plane or a master Node but a worker, we can't force the Operator to be deployed on a master node that doesn't exist. Instead, we want to deploy it on a worker. The proposal here is to relax the rule and use `preferredDuringSchedulingIgnoredDuringExecution` instead so the scheduler will try to find a master node or fallback on other nodes if not found.
3261be4
to
8950f76
Compare
In the context of Hypershift (Hosted Clusters with OpenShift), where a Nodepool
(terminology for a worker Node in HCP) is not a control-plane or
a master Node but a worker, we can't force the Operator to be deployed
on a master node that doesn't exist. Instead, we want to deploy it on a
worker.
The proposal here is to relax the rule and use
preferredDuringSchedulingIgnoredDuringExecution
instead so the schedulerwill try to find a master node or fallback on other nodes if not found.