Typically, valid ingresses created on openshift automatically have a corresponding route created for them by the appropriate controllers and routers, and the ingress resource's status is updated with the host information from the backing route

Currently, ingresses created by the operator (by setting spec.server.ingress to enabled) don't appear to be accepted by the ingress controller on openshift, because the status field remains unpopulated and the ingress is not really usable 

This bug might require investigating the ingress that is created by the operator 

Acceptance criteria

• ingresses created by the operator should be accepted by the ingress controller and have a corresponding route created for them automatically on openshift