<p>In <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/ingress" rel="noreferrer">GKE Ingress documentation</a>
it states that:</p>
<blockquote>
<p><em>When you create an Ingress object, the GKE Ingress controller creates a Google Cloud HTTP(S) Load Balancer and configures it according to the information in the Ingress and its associated Services.</em></p>
</blockquote>
<p>To me it seems that I can not have multiple <a href="https://kubernetes.io/docs/concepts/services-networking/ingress/" rel="noreferrer">ingress resources</a> with single GCP ingress controller. Instead, GKE creates a new ingress controller for every ingress resource.</p>
<p>Is this really so, or is it possible to have multiple ingress resources with a single ingress controller in GKE?</p>
<p>I would like to have one GCP LoadBalancer as ingress controller with static IP and DNS configured, and then have multiple applications running in cluster, each application registering its own ingress resource with application specific host and/or path specifications.</p>
<p>Please note that I'm very new to GKE, GCP and Kubernetes in general, so it might be that I have misunderstood something.</p>

<p>I think the question you're actually asking is slightly different than what you have written.  You want to know if multiple Ingress resources can be linked to a single GCP Load Balancer, not GKE Ingress controller. Based on the <a href="https://kubernetes.io/docs/concepts/architecture/controller/" rel="noreferrer">concept of a controller</a>, there is only one GKE Ingress controller in a cluster, which is responsible for fulfilling multiple resources and provisioning multiple load balancers.</p>
<p>So, to answer the question directly (because I've been searching for a straight answer for a long time!):</p>
<blockquote>
<p>Combining multiple Ingress resources into a single Google Cloud load
balancer is not supported.</p>
</blockquote>
<p>Source: <a href="https://cloud.google.com/kubernetes-engine/docs/concepts/ingress" rel="noreferrer">https://cloud.google.com/kubernetes-engine/docs/concepts/ingress</a></p>
<p>Sad.</p>
<p>However, using the nginx-ingress controller is one way to at least minimize the number of external (GCP) load balancers provisioned (it only provisions a single TCP load balancer), but since the load balancer is for TCP traffic, it cannot terminate SSL, or apply Firewall rules for you (Cloud Armor cannot be used, for instance).</p>
<p>The only way I know of to have a single HTTPS load-balancer in GCP terminate SSL and route traffic to multiple services in GKE is to combine the ingresses into a single resource with all paths and certificates defined in one place.</p>
<p>(If anybody figures out a way to do it with multiple separate ingress resources, I'd love to hear it!)</p>
