Is it possible to create an GKE ingress that can accept http traffic over the 443 port?
My use case mean's that I am unable to use the HTTP(s) load balancers SSL resolution, as I need to have more than the 13-14 certificate limit. Currently I am using a Load balancer server in GKE, this creates a TCP load balancer in Google Cloud, works wonders. Except I'm looking into using the Geo Location features of the HTTP(s) load balancers, which as far as I can see aren't available with the TCP LB.
I did try to create an ingress with http on 443 but it just reports backends as unhealth.
My infrastructure is as follows:
|
v
TCP LB (Created by Loadbalancer Service)
|
v
Nginx Proxy (Only resolves SSL)
|
v
HTTP(s) LB (Created by K8S Ingress)
|
v
Many Services
Accessing the Geo Location from the HTTP(s) LB results in the Geo location of the Nginx proxy.
What I'm trying to achieve:
|
v
HTTP(s) LB (Created by K8S Ingress) [Adds GEO headers]
|
v
Nginx Proxy (Only resolves SSL)
|
v
HTTP(s) LB (Created by K8S Ingress)
|
v
Many Services
Would be much appreciated if anyone knows a solution or if can't use the built in Geo location at all.