-
Notifications
You must be signed in to change notification settings - Fork 13
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
Prefer Scheduling on OCP Infra Nodes #109
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: razo7 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 |
/test 4.14-openshift-e2e |
Infra nodes are a better fit than control plane nodes on OCP, thus we prefer NMO pod to be scheduled on an infra node over a control plane node
/test 4.15-openshift-e2e |
config/manager/manager.yaml
Outdated
preference: | ||
matchExpressions: | ||
- key: node-role.kubernetes.io/infra | ||
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 using Exists
without values
is a safer bet
config/manager/manager.yaml
Outdated
- key: node-role.kubernetes.io/master | ||
operator: Exists | ||
- matchExpressions: | ||
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.
In
doesn't make sense without values
, this needs to be Exists
config/manager/manager.yaml
Outdated
- key: node-role.kubernetes.io/control-plane | ||
operator: Exists | ||
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.
same here
config/manager/manager.yaml
Outdated
- effect: NoSchedule | ||
key: node-role.kubernetes.io/infra | ||
operator: Exists | ||
value: reserved |
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.
value
does not make sense with Exists
, only with Equal
. But using no value is better as suggested above, I'd remove value
config/manager/manager.yaml
Outdated
- effect: NoExecute | ||
key: node-role.kubernetes.io/infra | ||
operator: Exists | ||
value: reserved |
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.
same
Safer and relaxed and taint conditions using exist rather than empty In or specefic In
/test 4.14-openshift-e2e |
1 similar comment
/test 4.14-openshift-e2e |
/lgtm |
/retest |
Infra nodes are a better fit than control plane nodes on OCP, thus we prefer NMO pod to be scheduled on an infra node over a control plane node.
See pod scheduling weight and Infra Node.
ECOPROJECT-1660