Skip to content
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

Ensure nodeSelector logic is consistent for all operators #466

Merged

Conversation

olliewalsh
Copy link
Contributor

@olliewalsh olliewalsh commented Nov 15, 2024

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

Switch to a pointer for nodeSelector to allow different logic for empty vs unset
@openshift-ci openshift-ci bot requested review from abays and viroel November 15, 2024 17:38
@olliewalsh
Copy link
Contributor Author

/hold until the first PR has been reviewed openstack-k8s-operators/nova-operator#894

There is no need drop empty nodeSelector maps, omitempty already does this
@@ -230,6 +231,14 @@ func GetCinderVolume(name types.NamespacedName) *cinderv1.CinderVolume {
return instance
}

func GetCronJob(name types.NamespacedName) *batchv1.CronJob {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, also for keystone where this came from

@olliewalsh
Copy link
Contributor Author

/test cinder-operator-build-deploy-tempest

Copy link
Contributor

openshift-ci bot commented Nov 19, 2024

@olliewalsh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/cinder-operator-build-deploy-kuttl 0fd9df2 link true /test cinder-operator-build-deploy-kuttl
ci/prow/cinder-operator-build-deploy-tempest 0fd9df2 link false /test cinder-operator-build-deploy-tempest

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@olliewalsh
Copy link
Contributor Author

/remove-hold

Copy link
Contributor

@stuggi stuggi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

Copy link
Contributor

openshift-ci bot commented Nov 20, 2024

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit 9e97663 into openstack-k8s-operators:main Nov 20, 2024
8 checks passed
@olliewalsh
Copy link
Contributor Author

/cherry-pick 18.0-fr1

@openshift-cherrypick-robot

@olliewalsh: new pull request created: #469

In response to this:

/cherry-pick 18.0-fr1

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants