[18.0-fr1] Ensure nodeSelector logic is consistent for all operators

[openshift-cherrypick-robot]

This is an automated cherry-pick of #466

/assign olliewalsh

[abays]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abays, openshift-cherrypick-robot

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:

• OWNERS [abays]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[olliewalsh]

/test cinder-operator-build-deploy

[olliewalsh]

/test cinder-operator-build-deploy-tempest

[abays]

/test cinder-operator-build-deploy-kuttl

{  failed to wait for the created cluster claim to become ready: timed out waiting for the condition}

/test cinder-operator-build-deploy-kuttl

[olliewalsh]

/override ci/prow/cinder-operator-build-deploy ci/prow/cinder-operator-build-deploy-kuttl ci/prow/cinder-operator-build-deploy-tempest
will create follow-up DNM PRs to test as there is a circular dependency with the openstack-operator patch

[openshift-ci]

@olliewalsh: Overrode contexts on behalf of olliewalsh: ci/prow/cinder-operator-build-deploy, ci/prow/cinder-operator-build-deploy-kuttl, ci/prow/cinder-operator-build-deploy-tempest

In response to this:

/override ci/prow/cinder-operator-build-deploy ci/prow/cinder-operator-build-deploy-kuttl ci/prow/cinder-operator-build-deploy-tempest
will create follow-up DNM PRs to test as there is a circular dependency with the openstack-operator patch

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.