OCPBUGS-63449: filter ingress namespace on UnmanagedRoutes metric#71
Conversation
Route controller triggers the UnmanagedRoutes metric whenever an unmanaged Ingress resource owns a Route resource. An ingress is considered managed when it points to an existing ingress class, and this ingress class configures spec.controller as "openshift.io/ingress-to-route" controller. The management check was incorrectly filtering ingress resources by missing to check its namespace, so a managed ingress that owns a router would be considered unmanaged if an unmanaged ingress on another namespace shares the same name.
|
@jcmoraisjr: This pull request references Jira Issue OCPBUGS-63449, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
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. |
|
/retest |
|
@jcmoraisjr: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
Reproduced it with 4.22.0-0.nightly-2026-01-24-213011 by using the customer's configuration Couldn't reproduced it with 4.22.0-0-2026-01-27-054839-test-ci-ln-dpj060k-latest |
|
/label qe-approved |
|
@jcmoraisjr: This pull request references Jira Issue OCPBUGS-63449, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: DetailsIn response to this:
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. |
|
@ShudiLi: This PR has been marked as verified by DetailsIn response to this:
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. |
|
As discussed, for the future, we add Jira issue number to the commit message too. /lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alebedev87, jcmoraisjr The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@jcmoraisjr: Jira Issue Verification Checks: Jira Issue OCPBUGS-63449 Jira Issue OCPBUGS-63449 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 DetailsIn response to this:
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. |
|
Fix included in accepted release 4.22.0-0.nightly-2026-01-28-225830 |
|
/cherry-pick release-4.21 release-4.20 release-4.19 |
|
@jcmoraisjr: new pull request created: #73 DetailsIn response to this:
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. |


Route controller triggers the UnmanagedRoutes metric whenever an unmanaged Ingress resource owns a Route resource. An ingress is considered managed when it points to an existing ingress class, and this ingress class configures spec.controller as "openshift.io/ingress-to-route" controller.
The management check was incorrectly filtering ingress resources by missing to check its namespace, so a managed ingress that owns a router would be considered unmanaged if an unmanaged ingress on another namespace shares the same name.