Problem

When using the serving.knative.openshift.io/disableRoute=true annotation, the knative service displays an invalid URL in .status.url field. The URL that is listed there doesn't resolve to the knative service. The invalid URL is misleading and shouldn't be shown.

It is also worth to mention that OpenShift Console UI and knative client CLI both display that invalid address in multiple places.

The Knative Route is also created, and the .status.url field also contains the invalid URL.

Proposals

If the serving.knative.openshift.io/disableRoute=true annotation is being used, we either should use a NULL value as the URL for .status.url fields, or used a cluster local URL.

If we choose to use NULL value in that case, we should make sure that OpenShift UI and kn CLI will handle that NULL properly.

The best solution would be to detect that user is defined the DomainMapping CR, and if that's the case, use that custom domain in .status.url fields. That can't be done if the user is using kn CLI to create a service, as in the end the CLI will display a text similar to:

Service 'showcase' created to latest revision 'showcase-00001' is available at URL:
http://showcase-demo.apps.openshift.example.net

Further improvement would be to detect that the user had created a custom OpenShift TLS Route, and if that's the case, display an HTTPS variant of the custom URL.