[release-4.18] OCPBUGS-51163: Fix bad IPv6 address

[jmesnil]

Let the kube-rbac-proxy listens on 8443 (without specifying the IP address)

In the insights-operator, connect to this port to go through the kube-rbac-proxy

This fixes https://issues.redhat.com/browse/OCPBUGS-51163

I've also cherry-picked a commit for https://issues.redhat.com/browse/OCPBUGS-51164 as it was fixed in master by OCPBUGS-45926: use joinHostPort to fix IPv6 but is also necessary on 4.18 to connect on an IPv6 cluster

Categories

• Bugfix
• Backporting

References

https://issues.redhat.com/browse/OCPBUGS-51163
https://issues.redhat.com/browse/OCPBUGS-51164

Upstream PR is #1073

[openshift-ci-robot]

@jmesnil: This pull request references Jira Issue OCPBUGS-51163, 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-51109 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

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

In response to this:

Let the kube-rbac-proxy listens on 8443 (without specifying the IP address)

In the insights-operator, connect to this port to go through the kube-rbac-proxy

This fixes https://issues.redhat.com/browse/OCPBUGS-51163

I've also cherry-picked a commit for https://issues.redhat.com/browse/OCPBUGS-51164 as it was fixed in master by OCPBUGS-45926: use joinHostPort to fix IPv6 but is also necessary on 4.18 to connect on an IPv6 cluster

Categories

• Bugfix
• Backporting

References

https://issues.redhat.com/browse/OCPBUGS-51163
https://issues.redhat.com/browse/OCPBUGS-51164

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.

[jmesnil]

/payload-job periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6-techpreview

[openshift-ci]

@jmesnil: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ipi-ovn-ipv6-techpreview

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/84f39f40-f287-11ef-9e00-aa063f638c80-0

[jmesnil]

/test unit

[tremes]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmesnil, tremes

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

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

[tremes]

/retest

[openshift-ci]

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

[tremes]

/label backport-risk-assessed

[tremes]

/jira refresh

[openshift-ci-robot]

@tremes: This pull request references Jira Issue OCPBUGS-51163, 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-51109 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA 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

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.