<p>I need help for the right workflow for developing with Jhipster when there is no local service discovery.</p>

<p>In my current private projects I used Jhipster registry for service discovery, and OAuth2 (Keycloak). Everything were deployed to Kubernetes, which worked perfectly.</p>

<p>Now I want to switch to Istio. Therefore I selected the option 'serviceDiscoveryType' : false.</p>

<p>In a kubernetes environment this probably works because the ingress definition handles routing. I haven't tried that yet.</p>

<p>My problem at this point is that I don't know how to develop locally without this. When I start a simple gateway (port 8080), which connects to a microservice (port 8081), I get an error, because it looks for the microservice at port 8080.</p>

<p>At this point I want to add, that everything is secured by Oauth2 (Keycloak).</p>

<p>Is there a possibility to route the secured calls to the right port (8081), maybe an option in 'webpack.dev.js'?</p>

<p>Thanks for any advice.</p>

user1651904
<p>that's one issue we will cover in the future in jhipster. But currently here is what you can do:</p>

<ol>
<li><p>inner load balancing: when starting your services in docker-compose (chack out <a href="https://www.jhipster.tech/docker-compose/" rel="nofollow noreferrer">jhipster docker-compose</a>, then you can access the services the same as in kubernetes. If you have a "foo-app" running, you can exec into any container and <code>curl http://foo-app/</code> and get routed correctly.</p></li>
<li><p>edge routing: in kubernetes you can define several ingress paths, to make example.com/ routing to gateway:8080, example.com/foo routing to foo:8081 (if that's the configuration). Docker-compose itself doesn't have any feature for that. However, you can solve that by building an NGINX reverse proxy for that.</p></li>
</ol>

<p>Check out that: <a href="https://medium.com/@joatmon08/using-containers-to-learn-nginx-reverse-proxy-6be8ac75a757" rel="nofollow noreferrer">https://medium.com/@joatmon08/using-containers-to-learn-nginx-reverse-proxy-6be8ac75a757</a></p>

<p>it explains pretty good how to setup something similar</p>
