<p>I have a number of Services running against Pods hosted within a cluster on Google Cloud K8's.</p>

<p><strong>Service 1</strong> is an Ingress - <code>basic-ingress</code></p>

<p><strong>Service 2</strong> is a NodeJS API Gateway w/ 2 Pods - <code>security-gateway-svc</code></p>

<p><strong>Service 3</strong> is a NodeJS API w/ 2 Pods - <code>some-random-api-svc</code></p>

<p>and so on service 4 / 5 / 6 etc....</p>

<p>My Ingress allows me to access exposed services via a sub domain however I would like to move my external API's behind my Gateway so I can handle auth etc in the gateway.</p>

<p>What I'd like to do is allow <code>security-gateway-svc</code> to connect to <code>some-random-api-svc</code> without having to go via dns or outside of my cluster.</p>

<p>I figured I could update my ingress so all sub domains use the same service entry and allow the Gateway to figure out where the traffic should go.</p>

<p>I can configure this just fine locally as everything runs on <code>localhost</code> and I specify a <code>port</code> so it's fairly straight forward.</p>

<p>Is it possible however to expose pods to other pods within a cluster via the service name instead of an actual domain / dns look up?</p>

Tim J
<p>You service should be accessible within your cluster via the service name.</p>

<p>Point your gateway entry for each api to the service name.</p>

<p>Something like <code>http://some-random-api-svc</code> should work. </p>
