Question

Your team runs a public marketing site fronted by a global external Application Load Balancer. A new feature requires exposing an HTTP-triggered Cloud Run functions (formerly Cloud Functions 2nd gen) function under the path /api/subscribe on the same domain and certificate as the existing site. You must route requests to the function through the existing load balancer without provisioning any VMs or managing instance groups. What is the correct way to attach the function as a backend?

Accepted Answer

Create a serverless network endpoint group (NEG) that references the Cloud Functions service, add it as a backend to a backend service, and configure the URL map to route /api/subscribe to that backend service.

Answer

Create a zonal NEG of type GCE_VM_IP_PORT pointing to the function's runtime instances and attach it to a new backend service.

Answer

Create an internet NEG with the function's *.cloudfunctions.net FQDN and add it as a backend so the load balancer treats it as an external origin.

Answer

Create a backend bucket that maps to the Cloud Functions deployment and reference it in the URL map for the /api/subscribe path.