OCPNODE-2099: add kube-rbac-proxy-crio toleration change

[rphillips]

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

• Allow static pod tolerations (this PR): 4.16/master : Backport to EUS 4.14
• MCO Kube-Rbac-Proxy Static pods 4.16/master : OCPNODE-2098: Add static pod for kube-rbac-proxy-crio machine-config-operator#4175 : Backport to EUS 4.14
• Create an upgrade edge after all backports merge

After all the above backports are merged, then

• Change the Monitoring Operator to use port 9637 (with client certificates) : OCPNODE-2100: jsonnet: update crio port to TLS port 9637 cluster-monitoring-operator#2257 : This PR is only for 4.16

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.16.0" version, but no target version was set.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

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.

[rphillips]

/jira refresh

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

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.

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

This PR will need to be backported to EUS 4.14.

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.

[rphillips]

/assign @deads2k

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

Allow the static pod tolerations within origin tests (this PR)

4.16/master : Backport to 4.14

MCO Kube-Rbac-Proxy Static pods

4.16/master : openshift/machine-config-operator#4175 : Backport EUS 4.14

After all the above backports are done, then merge

change the Monitoring Operator to use port 9637 (with client certificates)

openshift/cluster-monitoring-operator#2257 : This PR is only for 4.16

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.

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

Allow the static pod tolerations within origin tests (this PR)

4.16/master : Backport to 4.14

MCO Kube-Rbac-Proxy Static pods

4.16/master : openshift/machine-config-operator#4175 : Backport EUS 4.14

After all the above backports are done, then

change the Monitoring Operator to use port 9637 (with client certificates)

openshift/cluster-monitoring-operator#2257 : This PR is only for 4.16

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.

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

• Allow static pod tolerations (this PR): 4.16/master : Backport to EUS 4.14
• MCO Kube-Rbac-Proxy Static pods 4.16/master : OCPNODE-2098: Add static pod for kube-rbac-proxy-crio machine-config-operator#4175 : Backport to EUS 4.14
• Create an upgrade edge after all backports merge

After all the above backports are merged, then

• Change the Monitoring Operator to use port 9637 (with client certificates)

openshift/cluster-monitoring-operator#2257 : This PR is only for 4.16

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.

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

• Allow static pod tolerations (this PR): 4.16/master : Backport to EUS 4.14
• MCO Kube-Rbac-Proxy Static pods 4.16/master : OCPNODE-2098: Add static pod for kube-rbac-proxy-crio machine-config-operator#4175 : Backport to EUS 4.14
• Create an upgrade edge after all backports merge

After all the above backports are merged, then

• Change the Monitoring Operator to use port 9637 (with client certificates)

openshift/cluster-monitoring-operator#2257 : This PR is only for 4.16

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.

[openshift-ci-robot]

@rphillips: This pull request references OCPNODE-2099 which is a valid jira issue.

In response to this:

kube-rbac-proxy-crio is a new static pod in the openshift-machine-config-operator namespace. Since it is a static pod, the tolerations test needs to ignore this pod due to it tolerating all taints.

openshift-machine-config-operator/kube-rbac-proxy-crio-ip-10-0-112-244.us-west-2.compute.internal tolerates all taints

Merge information

• Allow static pod tolerations (this PR): 4.16/master : Backport to EUS 4.14
• MCO Kube-Rbac-Proxy Static pods 4.16/master : OCPNODE-2098: Add static pod for kube-rbac-proxy-crio machine-config-operator#4175 : Backport to EUS 4.14
• Create an upgrade edge after all backports merge

After all the above backports are merged, then

• Change the Monitoring Operator to use port 9637 (with client certificates) : OCPNODE-2100: jsonnet: update crio port to TLS port 9637 cluster-monitoring-operator#2257 : This PR is only for 4.16

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.

[rphillips]

/cherry-pick release-4.15

[openshift-cherrypick-robot]

@rphillips: once the present PR merges, I will cherry-pick it on top of release-4.15 in a new PR and assign it to you.

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.

[deads2k]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, rphillips

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:

• test/extended/operators/OWNERS [deads2k]

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

[openshift-ci]

@rphillips: 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/e2e-aws-ovn-single-node-upgrade	c759a19	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-sdn	c759a19	link	false	/test e2e-metal-ipi-sdn
ci/prow/e2e-aws-ovn-single-node	c759a19	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-serial	c759a19	link	false	/test e2e-aws-ovn-single-node-serial

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-cherrypick-robot]

@rphillips: new pull request created: #28637

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.

[openshift-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.16.0-202403060709.p0.gba887b4.assembly.stream.el8 for distgit openshift-enterprise-tests.
All builds following this will include this PR.