[release-4.20] OCPBUGS-65664: IngressOperator not exposing some metrics for degraded…

[openshift-cherrypick-robot]

This is an automated cherry-pick of #1290

/assign davidesalerno

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-61508 has been cloned as Jira Issue OCPBUGS-65664. Will retitle bug to link to clone.
/retitle [release-4.20] OCPBUGS-65664: IngressOperator not exposing some metrics for degraded…

In response to this:

This is an automated cherry-pick of #1290

/assign davidesalerno

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-65664, 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-61508 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.

In response to this:

This is an automated cherry-pick of #1290

/assign davidesalerno

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:
Once this PR has been reviewed and has the lgtm label, please assign grzpiotrowski 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

[lihongan]

/jira refresh

[openshift-ci-robot]

@lihongan: This pull request references Jira Issue OCPBUGS-65664, 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-61508 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.

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.

[davidesalerno]

/test e2e-gcp-operator

[davidesalerno]

/jira refresh

[openshift-ci-robot]

@davidesalerno: This pull request references Jira Issue OCPBUGS-65664, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-61508 is in the state Release Pending (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-61508 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

Requesting review from QA contact:
/cc @ShudiLi

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.

[ShudiLi]

Tested it with 4.20.0-0-2025-11-19-032318-test-ci-ln-n2n32nb-latest

1.
% oc get clusterversion
NAME      VERSION                                                AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.20.0-0-2025-11-19-032318-test-ci-ln-n2n32nb-latest   True        False         79m     Cluster version is 4.20.0-0-2025-11-19-032318-test-ci-ln-n2n32nb-latest

2. update the default secret of the default ingresscontroller, create 3 more custom ingress-controller(The last two had some domain)
% oc -n openshift-ingress-operator get ingresscontroller
NAME      AGE
default   157m
int1      18m
int22     18m
int33     18m
% oc -n openshift-ingress get pods                      
NAME                              READY   STATUS    RESTARTS   AGE
router-default-7d4b4f4cdb-d4mlk   1/1     Running   0          2m40s
router-default-7d4b4f4cdb-f7kgr   1/1     Running   0          2m39s
router-int1-79dbfc8655-b8zf2      1/1     Running   0          15m
router-int22-77d94589bc-fx2q2     1/1     Running   0          15m

3. delete the ingress-operator pod
% oc -n openshift-ingress-operator delete pod ingress-operator-5c6c9bfc57-pzcml
pod "ingress-operator-5c6c9bfc57-pzcml" deleted
% oc -n openshift-ingress-operator get pods                                    
NAME                                READY   STATUS    RESTARTS   AGE
ingress-operator-5c6c9bfc57-szqvs   2/2     Running   0          11s

4.  the stats of the all valid ingresscontroller are available
% oc -n openshift-ingress-operator rsh ingress-operator-5c6c9bfc57-szqvs       
Defaulted container "ingress-operator" out of: ingress-operator, kube-rbac-proxy
sh-5.1$ curl -s localhost:60000/metrics | grep -v controller_runtime | grep -v workqueue | grep -v go_ | grep controller
# HELP ingress_controller_aws_nlb_active Report the number of active NLBs on AWS clusters.
# TYPE ingress_controller_aws_nlb_active gauge
ingress_controller_aws_nlb_active{name="default"} 0
ingress_controller_aws_nlb_active{name="int1"} 0
ingress_controller_aws_nlb_active{name="int22"} 0
# HELP ingress_controller_conditions Report the conditions for ingress controllers. 0 is False and 1 is True.
# TYPE ingress_controller_conditions gauge
ingress_controller_conditions{condition="Available",name="default"} 1
ingress_controller_conditions{condition="Available",name="int1"} 1
ingress_controller_conditions{condition="Available",name="int22"} 1
ingress_controller_conditions{condition="Degraded",name="default"} 0
ingress_controller_conditions{condition="Degraded",name="int1"} 0
ingress_controller_conditions{condition="Degraded",name="int22"} 0
# HELP route_metrics_controller_routes_per_shard Report the number of routes for shards (ingress controllers).
# TYPE route_metrics_controller_routes_per_shard gauge
route_metrics_controller_routes_per_shard{shard_name="default"} 8
route_metrics_controller_routes_per_shard{shard_name="int1"} 8
route_metrics_controller_routes_per_shard{shard_name="int22"} 8 

5. delete ingresscontoller int33 and check the ingress co
% oc get co ingress                                               
NAME      VERSION                                                AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
ingress   4.20.0-0-2025-11-19-032318-test-ci-ln-n2n32nb-latest   True        False         False      141m    

[ShudiLi]

/label qe-approved

[openshift-ci-robot]

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

• expected dependent Jira Issue OCPBUGS-61508 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:

This is an automated cherry-pick of #1290

/assign davidesalerno

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]

/verified by ShudiLi

[openshift-ci-robot]

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

In response to this:

/verified by @ShudiLi

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.

[davidesalerno]

/retest-required

[openshift-ci]

@openshift-cherrypick-robot: 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.

[lihongan]

/jira refresh

[openshift-ci-robot]

@lihongan: This pull request references Jira Issue OCPBUGS-65664, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.20.z) matches configured target version for branch (4.20.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-61508 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-61508 targets the "4.21.0" version, which is one of the valid target versions: 4.21.0
• bug has dependents

Requesting review from QA contact:
/cc @ShudiLi

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.

[davidesalerno]

/lgtm