Internal TCP/UDP load balancers not usable from other regions [111021512]

Fixed

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Jul 1, 2018 09:54PM

https://issuetracker.google.com/issues/78118489 tracks the goal of allowing an internal load balancer to have backends in multiple regions. My request is simpler: I'd like to be able to talk to an internal load balancer that is defined in region A from VMs in region B. All my backends are in the same region as the internal load balancer, but I want clients from other regions to be able to use it.

Setting up a load balancer on a VM isn't terribly hard to do once in a while for myself, but writing instructions for other people to set up multi-region deployments would be significantly easier if they could just run a command to create an internal load balancer.

Comments

nu...@google.com <nu...@google.com> #2Jul 2, 2018 08:15PM

Assigned to gc...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

It would be great if you can provide video and bugreport synced with the same timestamp.

oi...@bushelpowered.com <oi...@bushelpowered.com> #3Aug 24, 2018 10:06PM

What

More information

If I'm not mistaken, I need to reproduce the bug while the bug report is being generated, is that correct?

When

Time and frequency

Time when bug report was triggered: Apr 6, 2025 4:42 PM GMT+03:00

Where

Build and device data

- Build Number: google/panther_beta/panther:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251134035 (25.11.34 (260400-740024306))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Vodafone UA
SIM operator: Vodafone UA

Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

[Deleted User] <[Deleted User]> #4Oct 12, 2018 06:46AM

Information redacted by Android Beta Feedback.

se...@gmail.com <se...@gmail.com> #5Oct 18, 2018 05:13PM

What

More information

by the way, my friend, who also has a pixel 7, also noticed this bug, but since he is not participating in the beta testing program, he can't write about it here

Where

Build and device data

Debugging information
Google Play services
com.google.android.gms
Version 251134035 (25.11.34 (260400-740024306))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Vodafone UA
SIM operator: Vodafone UA

[Deleted User] <[Deleted User]> #6Nov 24, 2018 02:21PM

Information redacted by Android Beta Feedback.

ps...@gmail.com <ps...@gmail.com> #7Apr 24, 2019 07:28AM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

me...@imubit.com <me...@imubit.com> #8May 5, 2019 12:19AM

+1. GKE clusters for internal (in-cloud) use only are highly limited without this feature.
1. You cannot host databases accessible from other region
2. You cannot host internally used applications

[Deleted User] <[Deleted User]> #9Jun 25, 2019 03:18AM

be...@qoria.com <be...@qoria.com> #10Jun 25, 2019 05:33AM

se...@gmail.com <se...@gmail.com> #11Jun 26, 2019 02:42PM

Please implement this Google, is not that difficult and it will also help us not move to AZ or AM, we want to implement our solution using Google but without this feature, we will reconsider

[Deleted User] <[Deleted User]> #12Jul 4, 2019 11:00AM

I join the request, the ability to use a loadbalancer between regions will allow for more extensive solutions

ad...@gmail.com <ad...@gmail.com> #13Jul 9, 2019 05:56PM

ba...@gmail.com <ba...@gmail.com> #14Jul 13, 2019 12:09PM

Yes that's would be great for multi-cluster kubernetes setup across regions without having to expose services publicly.

ba...@gmail.com <ba...@gmail.com> #15Jul 17, 2019 10:31AM

ag...@gmail.com <ag...@gmail.com> #16Jul 17, 2019 12:36PM

bw...@gmail.com <bw...@gmail.com> #17Jul 21, 2019 04:07PM

ch...@rmgops.com <ch...@rmgops.com> #18Jul 31, 2019 05:10AM

k....@gmail.com <k....@gmail.com> #19Aug 8, 2019 07:45AM

https://issuetracker.google.com/issues/139012322

Message last modified on Aug 8, 2019 07:46AM

[Deleted User] <[Deleted User]> #20Aug 8, 2019 07:45AM

pa...@persistent.com <pa...@persistent.com> #21Aug 20, 2019 02:08PM

an...@movatic.co <an...@movatic.co> #22Aug 23, 2019 06:35PM

da...@nepa.com <da...@nepa.com> #23Sep 2, 2019 08:13AM

[Deleted User] <[Deleted User]> #24Sep 6, 2019 11:48AM

te...@viidakko.fi <te...@viidakko.fi> #25Sep 9, 2019 10:24AM

[Deleted User] <[Deleted User]> #26Sep 9, 2019 12:27PM

[Deleted User] <[Deleted User]> #27Sep 10, 2019 07:03PM

st...@gmail.com <st...@gmail.com> #28Sep 25, 2019 11:24AM

[Deleted User] <[Deleted User]> #29Oct 8, 2019 08:19AM

ja...@practiv.com <ja...@practiv.com> #30Oct 9, 2019 01:30AM

mi...@gmail.com <mi...@gmail.com> #31Oct 24, 2019 07:05PM

+1 Miles says DO IT

Lu...@bv-group.com <Lu...@bv-group.com> #32Nov 1, 2019 11:26AM

please DO

am...@gmail.com <am...@gmail.com> #33Nov 13, 2019 06:43AM

+1
This feels like a really important feature missed by GCP. I find it strange that internal pod IPs are accessible from any region and internal load balancers are not.

ma...@ridewithvia.com <ma...@ridewithvia.com> #34Nov 18, 2019 11:44AM

ru...@gmail.com <ru...@gmail.com> #35Dec 3, 2019 10:03AM

jw...@gmail.com <jw...@gmail.com> #36Dec 13, 2019 11:12AM

Hi All,

This can be solved by enabling global access on the forwarding rules of the ILB. As explained here:

https://cloud.google.com/load-balancing/docs/internal/setting-up-internal#ilb-global-access

Thanks to GCloud Support for helping with this solution

Joost

ge...@google.com <ge...@google.com> #37Jan 15, 2020 11:45PM

Marked as fixed, reassigned to ge...@google.com.

Thank you all for the valuable comments in this bug!

As suggested by the previous poster, GCP now allows you to configure an internal TCP/UDP load balancer such that it's available to clients in any region.

For more about this feature, please read:

https://cloud.google.com/load-balancing/docs/internal/#client_access

If you're new to internal TCP/UDP load balancing in GCP, I encourage you to read the whole overview:

https://cloud.google.com/load-balancing/docs/internal/

GKE 1.16 is required if you want to use this feature with Kubernetes Engine:

https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing#global_access_beta

Please note the following:

* Internal TCP/UDP load balancers are still regional (even when they are globally accessible). This means that all backend VMs (or node VMs) must be in one region. The load balancer's backend service and forwarding rule are still regional.

* For details about how global access interacts with networks connected to the load balancer's VPC network, please read:

https://cloud.google.com/load-balancing/docs/internal/internal-lb-and-other-networks

I'll mark this issue resolved. Thanks for using GCP!

Issue 111021512

Description

Issue summary

Comments

nu...@google.com <nu...@google.com> #2Jul 2, 2018 08:15PM

oi...@bushelpowered.com <oi...@bushelpowered.com> #3Aug 24, 2018 10:06PM

What

More information

When

Time and frequency

Where

Build and device data

[Deleted User] <[Deleted User]> #4Oct 12, 2018 06:46AM

se...@gmail.com <se...@gmail.com> #5Oct 18, 2018 05:13PM

What

More information

Where

Build and device data

[Deleted User] <[Deleted User]> #6Nov 24, 2018 02:21PM

ps...@gmail.com <ps...@gmail.com> #7Apr 24, 2019 07:28AM

me...@imubit.com <me...@imubit.com> #8May 5, 2019 12:19AM

[Deleted User] <[Deleted User]> #9Jun 25, 2019 03:18AM

be...@qoria.com <be...@qoria.com> #10Jun 25, 2019 05:33AM

se...@gmail.com <se...@gmail.com> #11Jun 26, 2019 02:42PM

[Deleted User] <[Deleted User]> #12Jul 4, 2019 11:00AM

ad...@gmail.com <ad...@gmail.com> #13Jul 9, 2019 05:56PM

ba...@gmail.com <ba...@gmail.com> #14Jul 13, 2019 12:09PM

ba...@gmail.com <ba...@gmail.com> #15Jul 17, 2019 10:31AM

ag...@gmail.com <ag...@gmail.com> #16Jul 17, 2019 12:36PM

bw...@gmail.com <bw...@gmail.com> #17Jul 21, 2019 04:07PM

ch...@rmgops.com <ch...@rmgops.com> #18Jul 31, 2019 05:10AM

k....@gmail.com <k....@gmail.com> #19Aug 8, 2019 07:45AM

[Deleted User] <[Deleted User]> #20Aug 8, 2019 07:45AM

pa...@persistent.com <pa...@persistent.com> #21Aug 20, 2019 02:08PM

an...@movatic.co <an...@movatic.co> #22Aug 23, 2019 06:35PM

da...@nepa.com <da...@nepa.com> #23Sep 2, 2019 08:13AM

[Deleted User] <[Deleted User]> #24Sep 6, 2019 11:48AM

te...@viidakko.fi <te...@viidakko.fi> #25Sep 9, 2019 10:24AM

[Deleted User] <[Deleted User]> #26Sep 9, 2019 12:27PM

[Deleted User] <[Deleted User]> #27Sep 10, 2019 07:03PM

st...@gmail.com <st...@gmail.com> #28Sep 25, 2019 11:24AM

[Deleted User] <[Deleted User]> #29Oct 8, 2019 08:19AM

ja...@practiv.com <ja...@practiv.com> #30Oct 9, 2019 01:30AM

mi...@gmail.com <mi...@gmail.com> #31Oct 24, 2019 07:05PM

Lu...@bv-group.com <Lu...@bv-group.com> #32Nov 1, 2019 11:26AM

am...@gmail.com <am...@gmail.com> #33Nov 13, 2019 06:43AM

ma...@ridewithvia.com <ma...@ridewithvia.com> #34Nov 18, 2019 11:44AM

ru...@gmail.com <ru...@gmail.com> #35Dec 3, 2019 10:03AM

jw...@gmail.com <jw...@gmail.com> #36Dec 13, 2019 11:12AM

ge...@google.com <ge...@google.com> #37Jan 15, 2020 11:45PM

Add comment

Issue metadata