persistent ingresswithoutclassname alerts w/no ingresses present. about cluster-ingress-operator HOT 10 CLOSED

No problem. Reported here: https://issues.redhat.com/browse/OCPBUGS-13181

from cluster-ingress-operator.

Hi @nate-duke, can you check for Prometheus metrics using the expression openshift_ingress_to_route_controller_ingress_without_class_name ? This is how the alert is generated. Maybe there are some lingering metrics that aren't being cleaned up.

from cluster-ingress-operator.

Hi @candita, thanks for looking into this. I did check that metric previously and it was steadily incrementing despite those cert-manager routes being created/destroyed. While I was doing the documentation to file this Issue we were updating our 4.12 cluster to the 4.12.0-0.okd-2023-04-16-041331 release and wouldn't you know it, after the update was complete the alerts all cleared.

Here's a 2 day snapshot of the sum of that metric though showing that it was >1 before but is 0 now. I'll have to see if it happens again once cert-manager has renewed a few certificates.

from cluster-ingress-operator.

@candita ok, so good(?) news! This came back after a few days:

However, only one classless ingress exists (the bottom one in the screenshot) which is unrelated and due to a users' poorly configured helm chart. The other two do not exist at all, yet are still alerting.

❯ kubectl get ingresses -A
NAMESPACE          NAME           CLASS    HOSTS                           ADDRESS                                            PORTS     AGE
REDACTED  REDACTED  <none>   REDACTED

They probably did exist at some point but the metric that's tracking them is just not getting cleaned up or decremented when they cease existing. I'm happy to help by providing any information you may need to help investigate this.

from cluster-ingress-operator.

This metric does continue to increase. 3 days ago there were 3 (one that actually existed) today the metric is 8 and none exist.

❯ kubectl get ingresses -A
No resources found

Please let me know if you need any more information or if there is a more appropriate place to report this issue. Thanks!

from cluster-ingress-operator.

We have fixed the Issue button so you may now report this in our bug list if you'd like. Our team will triage next week. Thanks for the report.

from cluster-ingress-operator.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from cluster-ingress-operator.

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

from cluster-ingress-operator.

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

from cluster-ingress-operator.

@openshift-bot: Closing this issue.

from cluster-ingress-operator.