How to setup Google Cloud Load Balancer for Cloud Run App, while maintaining the <xxxxxx>.a.run.app URL

0

votes

I would like to know how to go about setting up a Google Cloud Load Balancer for a Cloud Run App and would like to retain/use the same Cloud Run - .a.run.app URL

Is this possible? Could someone point me in the direction of some documentation. What I find in the GCP seems to only document use cases when a custom domain is setup for the load balancer, In my case I would like to stick to the run.app URL.

Thanks

google-cloud-rungoogle-cloud-load-balancer

Why do you want to add a load balancer if you use the same URL? What's your use case? What do you want to achieve? - guillaume blaquiere

Requests coming in from certain source machines (in the US region) seem to be getting blocked by the GFE. Both Cloud Run and the underlying Cloud Function URIs are returning the 403 Forbidden with the Google Robot only from these sources. All other requests are fine. Adding an external load balancer in addition to the Cloud Run load balancer we're hoping will fix the issue. - Trevor Lazarus

403 error can't be solved by a Load Balancer. The issue is something else! - guillaume blaquiere

Any ideas what else it can be? The worst part is those source machines are now starting to work and no longer being returned the 403. This has happened previously and fixed itself. - Trevor Lazarus

@guillaumeblaquiere, the issue was due to GFE blocking requests from our clients as they were wrongly mapped by GEO team as originating in an embargoed Country. Mapping team working on fixing this for us! Thanks again! - Trevor Lazarus

1 Answers

1

votes

The Cloud Run URL is controlled/managed by Google Cloud. This URL maps to the Google Frontend (GFE). You have no ability to redirect that mapping to an HTTP(S) Load Balancer.

Once you have configured the load balancer you can configure a new custom domain, but you will not be able to remap the existing URL to point to the load balancer.