Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-53077

metric for ingresswithoutclassname does not decrease when classless ingresses cease to exist

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • No
    • This is a legit bug in current versions. Customers have noticed it and care about it. Needs a priority re-evaluation. If truly minor then close it and end the false sense of hope that open bugs give.
    • None
    • Rejected
    • NI&D Sprint 268, NI&D Sprint 269, NI&D Sprint 270
    • 3
    • In Progress
    • Bug Fix
    • Hide
      * Previously, for an Ingress resource with an `IngressWithoutClassName` alert, the Ingress Controller did not delete the alert along with deletion of the resource. The alert continued to show on the {product-title} web console. With this release, the Ingress Controller resets the `openshift_ingress_to_route_controller_ingress_without_class_name` metric to `0` before the controller deletes the Ingress resource, so that the alert is deleted and no longer shows on the web console. (link:https://issues.redhat.com/browse/OCPBUGS-53077[*OCPBUGS-53077*])
      Show
      * Previously, for an Ingress resource with an `IngressWithoutClassName` alert, the Ingress Controller did not delete the alert along with deletion of the resource. The alert continued to show on the {product-title} web console. With this release, the Ingress Controller resets the `openshift_ingress_to_route_controller_ingress_without_class_name` metric to `0` before the controller deletes the Ingress resource, so that the alert is deleted and no longer shows on the web console. (link: https://issues.redhat.com/browse/OCPBUGS-53077 [* OCPBUGS-53077 *])
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-13181. The following is the description of the original issue:
      —
      Description of problem:

      We have an OKD 4.12 cluster which has persistent and 
increasing ingresswithoutclassname alerts with no ingresses normally 
present in the cluster. I believe the ingresswithoutclassname being 
counted is created as part of the ACME validation process managed by the
 cert-manager operator with it's openshift route addon which are torn down once the ACME validation is complete.

      Version-Release number of selected component (if applicable):

       4.12.0-0.okd-2023-04-16-041331

      How reproducible:

      seems very consistent. went away during an update but came back shortly after and continues to increase.

      Steps to Reproduce:

      1. create ingress w/o classname
2. see counter increase
3. delete classless ingress
4. counter does not decrease.

      Additional info:

      https://github.com/openshift/cluster-ingress-operator/issues/912

              mmasters1@redhat.com Miciah Masters
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Shudi Li Shudi Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: