Proposed as a stretch goal for Tech Preview, but can probably wait for GA.

1. As a customer, I would like to know when my Gateway has errors due to a DNS issue
2. As a customer, I would like to know when my Gateway has errors due to an LB issue
3. As a cluster admin, I would like to know when a Gateway has errors due to a DNS issue
4. As a cluster admin, I would like to know when my Gateway has errors due to an LB issue

Gateway API has status conditions for Gateways, but those should be managed by the implementation (Istio).  However, there may be errors that come up from our integration for which we want to set an easily viewed status instead of checking through logs to find such errors.  For example, OCPBUGS-31521 represents an error condition that we can solve by logging, alerting, and/or setting status.

Ingress Cluster Operator has its own status conditions and we manage them so we could add a new status that indicates when the Gateway API controllers encounter an error.

We intend to investigate having our own Operator dedicated to Gateway API, and in that case, we can add specific status conditions there.  Handling them within Ingress Cluster Operator as a start would only help.

Notes:

1. Documentation states that a Gateway MUST be created on "openshift-ingress" but Istio also manages Gateway outside of this annotation. CIO just creates DNS Records for Gateway inside openshift-ingress namespace, but Istio can also create LoadBalancers for Gateway outside of this namespace. We need to decide if we want to also reconcile/add conditions to Gateways outside of openshift-ingress but managed by our GatewayClass (openshift.io/gateway-controller/v1) or just Gateway managed on openshift-ingress namespace.