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
NO-JIRA: HyperShift code linter PR837 followup #910
NO-JIRA: HyperShift code linter PR837 followup #910
Conversation
PR456 introduced support for MachineConfig-like functionality for HyperShift via NTO. This PR unnecessarily creates a runtime.Scheme on every invocation of getMachineConfigFromConfigMap() and serializeMachineConfig() function as pointed out in PR837. Make the scheme an attribute of the controller and initialize it only once at controller instantiation.
@jmencak: GitHub didn't allow me to request PR reviews from the following users: jmencak. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jmencak 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 |
/cc @dagrayvid I have not tested this manually in HyperShift, as it can be quite time consuming. I believe this should be covered by the |
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.
thanks @jmencak this change indeed addresses my suggestion.
non-binding LGTM till we are sure the code is covered by tests (and only because we're not sure and checking)
@jmencak Yes that is right. I also checked the logs of the e2e-hypershift test to confirm:
/lgtm |
/retest-required |
/retest |
1 similar comment
/retest |
@jmencak: This pull request explicitly references no jira issue. 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. |
ci/prow/e2e-gcp-pao-updating-profile issues likely caused by https://issues.redhat.com/browse/OCPBUGS-26589 |
/retest |
/hold Revision 0de6589 was retested 3 times: holding |
/hold cancel |
@jmencak: 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. |
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-node-tuning-operator-container-v4.16.0-202401162251.p0.gf2f453f.assembly.stream for distgit cluster-node-tuning-operator. |
#456 introduced support for MachineConfig-like functionality for HyperShift via NTO. This PR unnecessarily creates a runtime.Scheme on every invocation of getMachineConfigFromConfigMap() and serializeMachineConfig() function as pointed out in #837 (comment). Make the scheme an attribute of the controller and initialize it only once at controller instantiation.
/cc