Case description:
The customer requires customized routes. The Operator automatically generates route hostnames for clients creating notebooks, pipelines, or serving, which can be problematic for platform/cluster admins due to long and unattractive names that exceed the allowed DNS characters limit.

The customer needs to modify this format to be user-friendly and shorter. They do not want the subdomain and cluster name in the URL as it restricts moving projects between clusters for load balancing.

Customer questions:

• We want a friendly name. How can we achieve this?
• have clients enter the names of notebook URLs etc instead of generating names by the operator. (And if the hostname is present we want to be able to reject that name, we can write a webhook for validation)
• is it possible for us to provide a custom logic (we can provide via API or write webhook) for route hostname generation that the operator can call?
• The customer wants to understand the behavior of using custom apps domain via ingress operator config. Does the operator use that to create routes for the dashboard or does it use the domain of openshift console?