OCPBUGS-28584: deploy: add get/list/watch permissions to infrastructure object

[flavianmissi]

this is used by library-go ControllerBuilder.Run to discover cluster topology and setup leader election based on that.

--

There isn't a lot of use in this for this operator as I doubt SNO clusters will be using the secondary scheduler 🤔
Regardless, this PR should silent the warn seen in the logs.

[openshift-ci-robot]

@flavianmissi: This pull request references Jira Issue OCPBUGS-28584, which is invalid:

• expected the bug to target the "4.16.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

this is used by library-go ControllerBuilder.Run to discover cluster topology and setup leader election based on that.

--

There isn't a lot of use in this for this operator as I doubt SNO clusters will be using the secondary scheduler 🤔
Regardless, this PR should silent the warn seen in the logs.

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.

[flavianmissi]

/jira refresh

[openshift-ci-robot]

@flavianmissi: This pull request references Jira Issue OCPBUGS-28584, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.16.0) matches configured target version for branch (4.16.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @kasturinarra

In response to this:

/jira refresh

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.

[ingvagabund]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flavianmissi, ingvagabund

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 [ingvagabund]

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

[openshift-ci]

@flavianmissi: The following test 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/security	a87c43e	link	false	/test security

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.

[openshift-ci-robot]

@flavianmissi: Jira Issue OCPBUGS-28584: All pull requests linked via external trackers have merged:

• openshift/secondary-scheduler-operator#126

Jira Issue OCPBUGS-28584 has been moved to the MODIFIED state.

In response to this:

this is used by library-go ControllerBuilder.Run to discover cluster topology and setup leader election based on that.

--

There isn't a lot of use in this for this operator as I doubt SNO clusters will be using the secondary scheduler 🤔
Regardless, this PR should silent the warn seen in the logs.

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.

[flavianmissi]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@flavianmissi: new pull request created: #127

In response to this:

/cherry-pick release-4.15

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.