Frank
2020-12-03 02:08:52
GKE Ingress is only for HTTP / HTTPS / "HTTP/2" (TLS) traffic, you can create a GKE TCP LB that points to the same backend you have on a different port.
Something like this:
apiVersion: "v1"
kind: "Service"
metadata:
name: "l4-loadbalancer"
namespace: "default"
labels:
app: "nginx"
spec:
ports:
- protocol: "TCP"
port: 80
targetPort: 80
selector:
app: "nginx"
type: "LoadBalancer"
loadBalancerIP: ""
You can also handle all of this by only using a GKE tcp load balancer, but the downside would be that you would need to handle your SSL certs on your backend directly, if you want GCP to handle this, then the 2 load balancer approach would be better.
The important bit that I missed was that an Ingress and LoadBalancer can link to the same back end through the labels. The expected down side to this is that it creates 2 load balancers.