-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.12
-
None
-
Low
-
No
-
Sprint 249, Sprint 250, Sprint 251, Sprint 252, Sprint 253
-
5
-
Rejected
-
False
-
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
- is duplicated by
-
OCPBUGS-32095 openshift_ingress_to_route_controller_ingress_without_class_name metrics is not reset to 0 after the Ingress resources being deleted
- Closed
- is related to
-
OCPBUGS-15253 Add namespace to IngressWithoutClassName and UnmanagedRoutes alert message
- Verified