[release-4.16] OCPBUGS-67000: Re-disable metrics server

[openshift-cherrypick-robot]

This is an automated cherry-pick of #2579

/assign openshift-cherrypick-robot

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-45086 has been cloned as Jira Issue OCPBUGS-67000. Will retitle bug to link to clone.
/retitle [release-4.16] OCPBUGS-67000: Re-disable metrics server

Details

In response to this:

This is an automated cherry-pick of #2579

/assign openshift-cherrypick-robot

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-67000, which is invalid:

• expected dependent Jira Issue OCPBUGS-45086 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

Details

In response to this:

This is an automated cherry-pick of #2579

/assign openshift-cherrypick-robot

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 jacobtanenbaum for approval. For more information see the Code Review Process.

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

Details

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/4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade-ipsec	80685e5	link	false	/test 4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade-ipsec
ci/prow/security	80685e5	link	false	/test security
ci/prow/4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade	80685e5	link	false	/test 4.16-upgrade-from-stable-4.15-e2e-aws-ovn-upgrade

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.

[qiowang721]

/verified by @qiowang721
pre-merge testing passed.
Steps:

1. build image with pr and setup compact OCP cluster
build 4.16,openshift/cluster-network-operator#2855

2. create a hostnetwork pod, listening on port 8080
% oc get pod -owide -n test
NAME        READY   STATUS    RESTARTS   AGE   IP           NODE                                       NOMINATED NODE   READINESS GATES
hello-pod   1/1     Running   0          5s    10.0.57.95   ip-10-0-57-95.us-east-2.compute.internal              

3. check on the node which hostnetowrk pod lands on, the pod is listening on port 8080
% oc debug node/ip-10-0-57-95.us-east-2.compute.internal
Temporary namespace openshift-debug-79trc is created for debugging node...
Starting pod/ip-10-0-57-95us-east-2computeinternal-debug-2zvp7 ...
To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
Pod IP: 10.0.57.95
If you don't see a command prompt, try pressing enter.
sh-5.1# netstat -tulpen | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      1000740000 1845726    184049/hello_opensh

4. check the network-operator pod is not in CrashLoopBackOff state, and there is no error message about metrics server
% oc get pod -n openshift-network-operator -l name=network-operator
NAME                                READY   STATUS    RESTARTS       AGE
network-operator-559646d665-6splz   1/1     Running   2 (103m ago)   117m
% oc describe pod/network-operator-559646d665-6splz -n openshift-network-operator | grep "metrics server"
% oc describe pod/network-operator-559646d665-6splz -n openshift-network-operator | grep "address already in use"
%

5. check cluster-network-operator is not DEGRADED
% oc get co | grep network
network                                    4.16.0-0-2025-12-10-015830-test-ci-ln-lky89fb-latest   True        False         False      117m

[openshift-ci-robot]

@qiowang721: This PR has been marked as verified by @qiowang721.

Details

In response to this:

/verified by @qiowang721
pre-merge testing passed.
Steps:

1. build image with pr and setup compact OCP cluster
build 4.16,openshift/cluster-network-operator#2855

2. create a hostnetwork pod, listening on port 8080
% oc get pod -owide -n test
NAME        READY   STATUS    RESTARTS   AGE   IP           NODE                                       NOMINATED NODE   READINESS GATES
hello-pod   1/1     Running   0          5s    10.0.57.95   ip-10-0-57-95.us-east-2.compute.internal              

3. check on the node which hostnetowrk pod lands on, the pod is listening on port 8080
% oc debug node/ip-10-0-57-95.us-east-2.compute.internal
Temporary namespace openshift-debug-79trc is created for debugging node...
Starting pod/ip-10-0-57-95us-east-2computeinternal-debug-2zvp7 ...
To use host binaries, run `chroot /host`. Instead, if you need to access host namespaces, run `nsenter -a -t 1`.
Pod IP: 10.0.57.95
If you don't see a command prompt, try pressing enter.
sh-5.1# netstat -tulpen | grep 8080
tcp6       0      0 :::8080                 :::*                    LISTEN      1000740000 1845726    184049/hello_opensh

4. check the network-operator pod is not in CrashLoopBackOff state, and there is no error message about metrics server
% oc get pod -n openshift-network-operator -l name=network-operator
NAME                                READY   STATUS    RESTARTS       AGE
network-operator-559646d665-6splz   1/1     Running   2 (103m ago)   117m
% oc describe pod/network-operator-559646d665-6splz -n openshift-network-operator | grep "metrics server"
% oc describe pod/network-operator-559646d665-6splz -n openshift-network-operator | grep "address already in use"
%

5. check cluster-network-operator is not DEGRADED
% oc get co | grep network
network                                    4.16.0-0-2025-12-10-015830-test-ci-ln-lky89fb-latest   True        False         False      117m

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.