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
OCPBUGS-25696: Apply Scheduling Configuration for kCCM #3382
OCPBUGS-25696: Apply Scheduling Configuration for kCCM #3382
Conversation
@orenc1: This pull request references Jira Issue OCPBUGS-25696, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
/jira refresh |
@orenc1: This pull request references Jira Issue OCPBUGS-25696, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (yli2@redhat.com), skipping review request. 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 openshift-eng/jira-lifecycle-plugin repository. |
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
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: davidvossel, orenc1 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 |
/hold Revision a48a07f was retested 3 times: holding |
/unhold |
/retest-required |
https://issues.redhat.com/browse/OCPBUGS-25696 kCCM deployment was not respecting the node selector configured at hcp.spec.nodeSelector that was set with --node-selector flag in the create cli command. This PR fixes the issue, by applying 'SetDefaults()' to the deploymentConfig, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)
a48a07f
to
eecee03
Compare
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
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
@orenc1: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
@orenc1: Jira Issue OCPBUGS-25696: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-25696 has been moved to the MODIFIED state. 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 openshift-eng/jira-lifecycle-plugin repository. |
/cherry-pick release-4.15 |
@orenc1: new pull request created: #3417 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/test-infra repository. |
/cherry-pick release-4.14 |
@orenc1: new pull request created: #3418 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/test-infra repository. |
Fix included in accepted release 4.16.0-0.nightly-2024-01-14-231715 |
What this PR does / why we need it:
kCCM deployment was not respecting the node selector configured at
hcp.spec.nodeSelector
that was set with--node-selector
flag in the create cli command. This PR fixes the issue, by applyingSetDefaults()
to thedeploymentConfig
, which sets the node selector along with other required configurations (e.g. tolerations, affinity, replica count, etc.)Which issue(s) this PR fixes
Fixes # https://issues.redhat.com/browse/OCPBUGS-25696
Checklist