<p>We have an Nginx ingress controller that we use as a Load Balancer. We have a control application that we use to create accounts for clients and when our control application creates the deployment it also upserts a service and an ingress. The ingress is used to route the traffic to a specific client backend service.</p>
<p><a href="https://i.stack.imgur.com/QAWpF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/QAWpF.png" alt="enter image description here" /></a></p>
<p>So any requests to <code>https://our.website.com/client/1</code> are routed to the <code>client-1</code> service and any requests to  <code>https://our.website.com/client/2</code> are routed to the <code>client-2</code> service.</p>
<p>Now our product has matured and we have the need to be able to deploy customer backends to different clusters. We have looked at creating a Multi-cluster implementation like GCP suggests in the <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/multi-cluster-services" rel="nofollow noreferrer">docs</a>. This is almost working for us but not exactly. The services can communicate with each other(we have other services also running) but NGINX is not able to see the Service Import. My question is does NGINX support mapping to Service Imports rather than just Services? If not is there a workaround to that or perhaps a different load balancer that would support that?</p>

Ilian Tetradev
<p>So I wasn't able to find a way to do that. We ended up implementing a mixed architecture where most of our apps such as the control ones and the React frontend are handled bt our current NGINX controller. We have also deployed a <code>gke-l7-gxlb-mc</code> Multi Cluster Gateway alongside out NGINX Load Balancer with a secondary URL <code>our-gw.website.com</code> This URL os used by our frontend only and is not visible to the clients.</p>
