<p>My problem is that I have seprate services for both the back and front ends when I go into a pod and run the curl <a href="http://backend" rel="nofollow noreferrer">http://backend</a> it resolves and communicates with the backend pod but then I put it into my angular as <a href="http://backend" rel="nofollow noreferrer">http://backend</a> it tells me it can't be resolved, How is it that the pods can communicate but the running application cant</p>

Conor Donohoe
<p>A <a href="https://kubernetes.io/docs/concepts/services-networking/service/" rel="nofollow noreferrer">Service</a> provides visibility inside the cluster. If you want to expose your Service to the outside world you need to use an <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="nofollow noreferrer">Ingress</a>.</p>

<p>P.D.: You could expose your services using NodePort but it is not recommended.</p>

<p>P.D. (2): If you already have a Backend Service and a Frontend Service, what makes sense is only to expose the frontend via ingress, and keep backend only reachable inside the cluster, to be consumed only from Frontend</p>
