NO-JIRA: operator/node-controller, guard-controller: parse the master node selector during construction

[p0lyn0mial]

while reviewing #1882 I found that the master nodes selector is being parsed on each sync for some controllers.

[openshift-ci-robot]

@p0lyn0mial: This pull request explicitly references no jira issue.

Details

In response to this:

while reviewing #1882 I found that the master nodes selector is being parsed on each sync for some controllers.

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.

[p0lyn0mial]

/hold

for a proof pr

[eggfoobar]

/lgtm

[p0lyn0mial]

/hold cancel

[p0lyn0mial]

@eggfoobar had to rebase the PR, PTAL.

[openshift-ci]

@p0lyn0mial: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[eggfoobar]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eggfoobar, p0lyn0mial

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• pkg/operator/staticpod/OWNERS [p0lyn0mial]

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