tldr - Can we connect a GKE Ingress LB to a GCP backend service which is connected to a backend group?
We have a project using Ingress to connect to various Kubernetes services which then talk to various pods in our cluster. We are using hosts and Google Managed Certficates to route traffic to these various services.
We have a separate GCP VM which is in a backend instance group attached to a backend service. Are we able to link this to the Ingress load balancer?
Editing within the cloud interface suggests it's possible, but obviously we can't change anything there as ingress manages this.
Adding a host area to ingress doesn't work as ingress says it cannot find the service, which has prefixed the backend service name with default/
So is this possible or will we have to create another GCP Load Balancer just to point to this service?
Kind regards
Jedi
Solved! Go to Solution.
Hi,
Yes, saw and read all that. Normal Kubernetes/Ingress/Services is fine, was just hoping to find a way to connect to backend services too, but looks like this is not possible.
So we've just created another load balancer to handle these requests.
Hi @jedihomer ,
May I know if you happen to follow or saw this documentation regarding GKE ingress for HTTP Load balancing? This explains that when you create an Ingress, it also creates a load balancer and configures it according to the information in the Ingress and its associated Services.
Hi,
Yes, saw and read all that. Normal Kubernetes/Ingress/Services is fine, was just hoping to find a way to connect to backend services too, but looks like this is not possible.
So we've just created another load balancer to handle these requests.
If you create an Ingress resource, you can't add a VM MIG backend via Ingress and if you try to edit the Load Balancer created by Ingress, eventually Ingress will reconcile it and overwrite your changes.
If you are good with two LBs, then that's a great solution.
If you wanted to have single load balancer, you can do this by manually creating a load balancer with two different backends. For the GKE backend, you would follow the guide on standalone NEGs.
But if the two LB solution works, it's simpler.