Feature Overview (aka. Goal Summary)  

Routes created under an ingress-sharded labeled namespace will get the route name from the custom ingress and not the default ingress.

Goals (aka. expected user outcomes)

When creating a route in an ingress-shared labeled namespace, it properly should have a route name from the (requested) custom ingress and not the default ingress.  Currently, a customer needs to explicitly mention --hostname when creating the route, to have it named correctly.

The request is to change the default behavior.

Requirements (aka. Acceptance Criteria):

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

1. What safe-guards need to be built to safely change the default behavior, considering the old behavior?

Out of Scope

• Customers can specify spec subdomain (YAML), but the ask here is to change the default behavior. 

  Customer Considerations

•  

Documentation Considerations