Say we have a service which serves at http://my-business-server:8080/business
In the past, under api-defination style, we could define such three api:
- /business -> http://my-business-server:8080 (strip url == false)
- /hide/client -> http://my-business-server:8080/business/client/r0 (strip url == true)
- /hide/media-> http://my-business-server:8080/business/media/r0 (strip url == true)
the 2. 3. mainly for hiding the word ‘business’ in url-path from our client.
Now we are moving the configuration to service/route style. But it seems that I cannot use just one service object with three route object to acheve the three forwarding rules above.
Is there a solution?
p.s. Why I do i expect using just one service defination. In my understanding the new Service/Route model is suit for SOA governance/service mesh, which treats ‘service’ as granularity and base unit. I hope the service defination could be neat(without define redundancy), and such there’s only one label (service=‘business’) in prometheus metrics, and only one (service=‘business’) in zipkin UI and so on.