OCPBUGS-65545: [release-4.20] add the missing service to the expose ports 22623 and 22624

[openshift-cherrypick-robot]

This is an automated cherry-pick of #5371

/assign aabughosh

[openshift-ci-robot]

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: MCO-1886

In response to this:

This is an automated cherry-pick of #5371

/assign aabughosh

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign dkhater-redhat for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

@openshift-cherrypick-robot: 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-gcp-op-1of2	95267b6	link	true	/test e2e-gcp-op-1of2
ci/prow/bootstrap-unit	95267b6	link	false	/test bootstrap-unit

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-sigs/prow repository. I understand the commands that are listed here.

[yuqi-zhang]

/jira cherrypick OCPBUGS-65544

[openshift-ci-robot]

@yuqi-zhang: Jira Issue OCPBUGS-65544 has been cloned as Jira Issue OCPBUGS-65545. Will retitle bug to link to clone.
/retitle OCPBUGS-65545: [release-4.20] add the missing service to the expose ports 22623 and 22624

In response to this:

/jira cherrypick OCPBUGS-65544

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]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-65545, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-65544 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead
• expected dependent Jira Issue OCPBUGS-65544 to target a version in 4.21.0, but it targets "4.21" instead

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 an automated cherry-pick of #5371

/assign aabughosh

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.

[yuqi-zhang]

/jira refresh

Will see if we can merge this alongside #5378

[openshift-ci-robot]

@yuqi-zhang: This pull request references Jira Issue OCPBUGS-65545, which is invalid:

• expected dependent Jira Issue OCPBUGS-65544 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

In response to this:

/jira refresh

Will see if we can merge this alongside #5378

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.

[aabughosh]

@yuqi-zhang can u approve?

[yuqi-zhang]

I was hoping to merge this alongside #5441 as one backport, since that simplifies the jira process, but it looks like that broke the pod entirely so I am trying to revert in #5445

Until then, this will not be able to merge since the bug will be invalid. Our options are then:

1. wait until we properly fix the kube-rbac-proxy pod, verify both via the bug, then merge this
2. create a completely separate backport chain bug for this and reattach the merged 4.21 PR to the new bug, and jira cherry-pick here

Which would you prefer