<p>So I have two clusters at the moment (soon to be a few more, once I get this working), ClusterA and ClusterB.</p>

<p>Is it possible for one ingress to interface with services from both clusters?</p>

<p>ClusterA hosts the front end and the ingress, while ClusterB hosts the back end.</p>

<p>The excerpted ingress is below. Everything bar the back end works.</p>

<pre><code>apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:{...}  
  selfLink: /apis/extensions/v1beta1/namespaces/default/ingresses/test-frontend-ingress
  uid: //
  spec:
  backend:
    serviceName: idu-frontend-XYZ
    servicePort: 80
  rules:
  - http:
      paths:
      - backend:
          serviceName: test-backend-app-service
          servicePort: 8080
        path: /api/v2/
      - backend:
          serviceName: idu-frontend-XYZ
          servicePort: 80
        path: /
  tls:
  - secretName: tls-cert-name
status:
  loadBalancer:
    ingress:
    - ip: 123.456.789.012

</code></pre>

<p>Back end service URL:<br>
<code>https://console.cloud.google.com/kubernetes/service/asia-southeast1-b/test-backend/default/test-backend-app-service...</code></p>

<p>URL the ingress tries to point to:<br>
<code>https://console.cloud.google.com/kubernetes/service/asia-southeast1-b/standard-cluster-1/default/test-backend-app-service...</code></p>

<p>So what I've gathered is the ingress can only interface with things in the same cluster as them? <code>test-backend</code> and <code>standard-cluster-1</code> are the cluster names, and they are both on the default namespace. Isn't that kind of pointless, as you can only deploy one thing to each cluster? Unless your images contain multiple apps, in which case it isn't really microservices anymore.</p>

sk0g
<p>Connecting two clusters with Kubernetes is hard I guess.</p>

<p>Instead you can deploy both the services on the same cluster. You can create two deployments and expose them as services. And then ingress can redirect traffic between them.</p>

<p>Why do you need a cluster per service though ? </p>

<p>If there is no other alternative you will have to do something like this: 
<a href="https://appscode.com/products/voyager/7.1.1/guides/ingress/http/external-svc/" rel="nofollow noreferrer">https://appscode.com/products/voyager/7.1.1/guides/ingress/http/external-svc/</a></p>
