The openshift_ingress_to_route_controller_ingress_without_class_name metrics is not reset to 0 after the Ingress resource being deleted.

As a result, the IngressWithoutClassName alert will keep in Firing state even if the Ingress resource that cause the alert has already been deleted.

4.14

Always

    1. Create a test Ingress resouce

$ cat ingress.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: minimal-ingress
spec:
  rules:
  - http:
      paths:
      - path: /testpath
        pathType: Prefix
        backend:
          service:
            name: hello-sinatra
            port:
              number: 8080

    2. Confirm the IngressWithoutClassName alert is in Pending state
   3. Confirm the openshift_ingress_to_route_controller_ingress_without_class_name metrics has a value equals to 1
    4. Delete the test Ingress resource
    5. Confirm the IngressWithoutClassName alert state and the openshift_ingress_to_route_controller_ingress_without_class_name metrics value

    The IngressWithoutClassName alert is still in Pending state because the openshift_ingress_to_route_controller_ingress_without_class_name metrics value is still 1.

   The openshift_ingress_to_route_controller_ingress_without_class_name metrics value is reset to 0 and the IngressWithoutClassName alert is resolved.