GCE ingress L4 Support

[Kripu77]

Hi all, given GCE ingress is a layer 7 load balancer is there any possibility of having layer 4 LB support in the future?

[swetharepakula]

L4 LB Support is available by configuring Service type LoadBalancer resources.

https://cloud.google.com/kubernetes-engine/docs/concepts/service-load-balancer

[Kripu77]

Hi Sweta, thank you for your response. I was looking for a workaround to have the ingress controller provision a Layer 4 load balancer, instead of directly using a service type as LoadBalancer in the service resource manifest.

[swetharepakula]

@Kripu77, can you expand more on why you would like to use the Ingress API over the Service API to configure/provision an L4 Load Balancer?

I am trying to understand what is missing from the existing Services API?

[swetharepakula]

/kind feature

[Kripu77]

@Kripu77, can you expand more on why you would like to use the Ingress API over the Service API to configure/provision an L4 Load Balancer?

I am trying to understand what is missing from the existing Services API?

@swetharepakula, we prefer using the Ingress API over the Service API to set up a Layer 4 Load Balancer because we want a single load balancer that can handle both Layer 4 and Layer 7 protocols. We use MQTT, which is a Layer 4 protocol, and we also have web services that uses Layer 7 (HTTP). Right now, with the current GCE ingress setup, we can't have just one load balancer for both types of traffic.

Because of this, we had to create a separate Layer 4 Load Balancer just for MQTT which is a cost implication as we need to reserve a static IP, provision a external load balancer, create multiple SSL certificates.

If GCE Ingress could work with both Layer 4 and Layer 7, we wouldn't need to do this.

Looking forward to your input if I'm wrong in above.

Thanks,
Kripu

[cezarygerard]

If I understand correctly you want just 1 kubernetes object and 1 IP address to provision both L7 and L4 load balancers?

This sounds like feature request for our Gateway API implementation https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api

We have this on the roadmap, but probably not this year

[Kripu77]

If I understand correctly you want just 1 kubernetes object and 1 IP address to provision both L7 and L4 load balancers?

This sounds like feature request for our Gateway API implementation https://cloud.google.com/kubernetes-engine/docs/concepts/gateway-api

We have this on the roadmap, but probably not this year

@cezarygerard you're correct. Any chance this feature making to GCE ingress as well?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale