Ensure nodeSelector logic is consistent for all operators #388
Conversation
Switch to a pointer for nodeSelector to allow different logic for empty vs unset
|
/hold until the first PR has been reviewed openstack-k8s-operators/nova-operator#894 |
|
/retest |
There is no need drop empty nodeSelector maps, omitempty already does this
|
/remove-hold |
|
/remove-hold |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: olliewalsh, stuggi 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 |
openshift-merge-bot
bot
merged commit c38568c
into
openstack-k8s-operators:main
|
/cherry-pick 18.0-fr1 |
|
@olliewalsh: new pull request created: #390 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
nodeSelectors are not currently applied consistently across all operators.
Some do not support nodeSelectors at all - will be implemented in this series of pull requests.
Some do not apply them to every pod (jobs/cronjobs esp) - will be resolved in this series of pull requests.
Some do not apply a node selector update correctly, only when not initially set.
Some support nodeSelectors but do not inherit the default nodeSelector from the OpenstackControlPlane CR.
Jira: OSPRH-10734