When creating a route (from a service) using `oc expose` (to align with our corporate cluster standards, we must label the route (to place the route on the correct router shard (using https://docs.openshift.com/container-platform/4.14/networking/ingress-sharding.html#nw-ingress-sharding-route-labels_ingress-sharding) thus we can use `oc expose -l LABEL` to accomplish this. 

However in addition to this each shard in our deployment also only provides routing to specific domains (IE: shard one (label=shard1 hosts foo.com, while shard two label=shard2 hosts bar.com). 

Thus we attempt combine `--hostname` and `--label` on the `oc expose` command to achieve the desired result of creating a route in one command; however this doesn't work.

You can use `--hostname` or `--label` independently but not together. 

Example (doesn't work): 

❯ NAME=foo SERVICE=service/$NAME oc expose $SERVICE --hostname $(oc get $SERVICE -o go-template="{{ .metadata.name }}")-$(oc project -q).foo.com -l shard=shard1

❯ oc version
Client Version: 4.11.0-202304181642.p0.gdea6f47.assembly.stream-dea6f47
Kustomize Version: v4.5.4
Kubernetes Version: v1.27.6+d548052


Cluster Version: v1.27.6+d548052

1. Set up Router Sharding (with labels) 

https://docs.openshift.com/container-platform/4.14/networking/ingress-sharding.html#nw-ingress-sharding-route-labels_ingress-sharding

2. Create a route using both the '--label` and '--hostname' cli options
    

You create a route with the proper hostname; but it doesn't have a label applied to it. 

You should get a route with both the correct (non default hostname) and with the correct sharding label