Closed robinmanuelthiel closed 4 years ago
I just ran into this too. It is fixed manually by editing the yaml for the rating-api service but I don't know if there is a more civilized way. So, either modify the docs to include a step to change port configuration for this service, or modify the rating-api repo to include configuration files that will automatically expose the correct port (I ignore if this is possible).
I just ran into this too. It is fixed manually by editing the yaml for the rating-api service but I don't know if there is a more civilized way. So, either modify the docs to include a step to change port configuration for this service, or modify the rating-api repo to include configuration files that will automatically expose the correct port (I ignore if this is possible).
Hi Pedrogok. Could you please describe the fix you made? Thanks.
I just ran into this too. It is fixed manually by editing the yaml for the rating-api service but I don't know if there is a more civilized way. So, either modify the docs to include a step to change port configuration for this service, or modify the rating-api repo to include configuration files that will automatically expose the correct port (I ignore if this is possible).
Hi Pedrogok. Could you please describe the fix you made? Thanks.
I can't remember the exact steps, since I already deleted this app. But more or less what I remember doing is in the Azure dashboard modifying some yaml related to this service in order to set the proper port. Hope that helps.
I hit the same issue. I went to the rating-api service and changed the yaml. Set the port and targetport to 3000.
API now uses port 8080.
The
ratings-api
, which is deployed in step 2.4 exposes port3000
. The service, that gets created by the following command exposes port8080
.This leads to misconfiguration and the web frontend can't find the api. The port exposed by the
ratings-api
service has to be changed from8080
to3000
manually.