We have deployed the bookinfo sample application on our cluster as means of making sure istio is working correctly and to demo it’s capabilities.
Due to company’s policies we had to change the service names to follow standard convention:
details —> xx-bookinfodetails-app
ratings —> xx-bookinforatings-app
productpage —> xx-bookinfoproductpage-app
reviews (all versions) —> xx-bookinforeviews-app
We have created a gateway and virtualService to route traffic to the first service ProductPage, which in turn is looking for other services (details/reviews) but now the application is “broken” since it is looking for http://details:9080 and http://reviews:9080 but now they don’t exist anymore.
I am new to istio and don’t know how to solve this and create some form of “translation or rewrite” so that internal requests to http://details would be actually forwarded to http://xx-bookinfodetails-app:9080.
I was trying playing with the productpage virtualservice, also tried creating virtualservices for details and reviews.
I’ve tried creating Destination (though not really knowing what would it help with).
I see that there’s something called ServiceEntry but I cannot find any example to handle internal traffic and quite frankly I didn’t really understand when to use SE.
Help would be highly appreciated