NE-2501: Allow prometheus test pods to access Ingress Operator metrics port

[rfredette]

New network policies in openshift/cluster-ingress-operator#1392 will limit access to the Ingress Operator's metrics port to only pods within the openshift-monitoring namespace. Similar to #30753, allow the metrics test pods to access the Ingress Operator's metrics port with an additional network policy.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@rfredette: This pull request references NE-2501 which is a valid jira issue.

Details

In response to this:

New network policies in openshift/cluster-ingress-operator#1392 will limit access to the Ingress Operator's metrics port to only pods within the openshift-monitoring namespace. Similar to #30753, allow the metrics test pods to access the Ingress Operator's metrics port with an additional network policy.

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ace8ad52-64a1-410a-a2f1-7d9c3258fd33

📥 Commits

Reviewing files that changed from the base of the PR and between 394edfe and 93065e7.

📒 Files selected for processing (1)

• test/extended/prometheus/prometheus.go

---

Walkthrough

The change adds a new Prometheus network policy target to the authentication test in the Prometheus test suite. Specifically, openshift-ingress-operator on port 9393 is included in the ports list for testing unauthorized access scenarios.

Changes

Cohort / File(s)	Summary
Test Network Policy Update test/extended/prometheus/prometheus.go	Added openshift-ingress-operator on port 9393 to the network policy ports list in the "should not be accessible without auth" test, expanding coverage of namespace/port combinations for authentication enforcement validation.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.11.3)

Error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions
The command is terminated due to an error: can't load config: unsupported version of the configuration: "" See https://golangci-lint.run/docs/product/migration-guide for migration instructions

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[rfredette]

@simonpasquier please take a look at this; same network policy issue as #30753, but for the ingress operator.

[simonpasquier]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rfredette, simonpasquier

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:

• test/extended/prometheus/OWNERS [simonpasquier]

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

[simonpasquier]

/verified by @simonpasquier

[openshift-ci-robot]

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

Details

In response to this:

/verified by @simonpasquier

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]

/retest-required

Remaining retests: 0 against base HEAD 394edfe and 2 for PR HEAD 93065e7 in total

[openshift-ci]

@rfredette: 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.