As part of https://bugzilla.redhat.com/show_bug.cgi?id=1962502 respectively https://github.com/openshift/enhancements/blob/master/enhancements/ingress/transition-ingress-from-beta-to-stable.md#risks-and-mitigations, the alert IngressWithoutClassName was introduced to help OpenShift Container Platform 4 - Cluster  Operator understand whether Ingress objects would exist without a ingressClassName specified. Given that without a ingressClassName specified, it's not clear what the ingress object is suppose to-do, it's key that alerting is taking place and actions are taken to set the ingressClassName properly for each ingress object.

OpenShift Container Platform 4.12

Always

1. Create Ingress object on OpenShift Container Platform 4.12 without ingressClassName specified
2. Check if IngressWithoutClassName is firing (or pending firing)
3. Patch the ingress object with ingressClassName and validate that the alert does disappear

Alert IngressWithoutClassName firing without Runbook being specified or documentation available, explaining the alert and action required to run.

The alert IngressWithoutClassName should have a runbook linked or the alert should be documented so customers understand what it's all about, what action needs to be taken and overall impact.