As a developer I want my endpoints to have TLS enabled by default. 

We are aligning Knative Route template in OpenShift to match the OpenShift default of

{{.Name}}-{{.Namespace}}.{{.Domain}}

instead of the Knative default of

 {{.Name}}.{{.Namespace}}.{{.Domain}}

This enables OpenShift wildcard TLS certificates working out of the box (we get TLS support for all Knative Services in the cluster out of the box), working Katacoda (it can't handle multiple subdomains), and general consistency in the URL space for OpenShift applications. The caveat is we need to handle the possible routing conflicts.

This will require changes in Kourier, serverless-operator for GA and we will be shipping a webhook to improve developer experience post-GA.

No intervention is necessary from end users perspective, though there will be a breaking change when upgrading from 1.6.0 as all requests to the old host will be dropped. We will be tracking release note changes in SRVKS-525.