gcloud

• To create and deploy a multi-region service, run thegcloud run deploy command using the--regions flag:

  gcloudrundeploySERVICE_NAME\--image=IMAGE_URL\--regions=REGIONS

  Replace the following:

  • SERVICE_NAME: The name of the multi-region servicethat you want to deploy.
  • IMAGE_URL: A reference to the container image, forexample,us-docker.pkg.dev/cloudrun/container/hello:latest.
  • REGIONS: The list of multiple regions that youwant to deploy to. For example,europe-west1,asia-east1.

YAML

1. Create theYAML file for your service, usingtherun.googleapis.com/regions attribute to set the multiple regions thatyou want to deploy your service to:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICE_NAMEannotations:run.googleapis.com/regions:REGIONSspec:template:spec:containers:-image:IMAGE_URL

   Replace the following:

   • SERVICE_NAME: The name of the multi-regionservice that you want to deploy to.
   • REGIONS: The list of multiple regions that youwant to update. For example,europe-west1,asia-east1.
   • IMAGE_URL: A reference to the container image, forexample,us-docker.pkg.dev/cloudrun/container/hello:latest.

2. Create the service using the following command:

   gcloudrunmulti-region-servicesreplaceservice.yaml

Terraform

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

Add the following to agoogle_cloud_run_v2_serviceresource in your Terraform configuration.

resource"google_cloud_run_v2_service""default"{name="cloudrun-service-multi-region"regions=["REGION_1","REGION_2",]template{containers{image="us-docker.pkg.dev/cloudrun/container/hello"}}}

Replace"REGION_1" and"REGION_2" with each of the neededGoogle Cloud regions. For example,europe-west1andus-central1.

1. To update an existing multi-region service, download itsYAML configuration:

   gcloudrunmulti-region-servicesdescribeSERVICE_NAME--formatexport>service.yaml

2. Update therun.googleapis.com/regions attribute to add or remove the listof regions that you want the service to deploy to:

   apiVersion:serving.knative.dev/v1kind:Servicemetadata:name:SERVICE_NAMEannotations:run.googleapis.com/regions:REGIONS

   Replace the following:

   • SERVICE_NAME: The name of the multi-regionservice that you want to deploy to.
   • REGIONS: The new list of multiple regions thatyou want the service revision to deploy to.

3. Update the service using the following command:

   gcloudrunmulti-region-servicesreplaceservice.yaml

gcloud

1. Reserve a static IP address so you don't have to update your DNS recordswhen you recreate your load balancer.

   gcloudcomputeaddressescreate--globalSERVICE_IP

   In the command above, replaceSERVICE_IP with a name for the IPaddress resource (e.g.myservice-ip).

   This IP address is a global anycast IPv4 address that routes to the Google datacenter or point of presence closest to your visitors.

2. Create a backend service.

   gcloudcomputebackend-servicescreate\--globalBACKEND_NAME\--load-balancing-scheme=EXTERNAL_MANAGED

   ReplaceBACKEND_NAME with a name you want to give to the backend service. For example,myservice-backend.

3. Create a URL map.

   gcloudcomputeurl-mapscreateURLMAP_NAME--default-service=BACKEND_NAME

   ReplaceURLMAP_NAME with a name you want to give to the URL map (e.g.myservice-urlmap).

4. Create a managed TLS certificate for your domain to serve HTTPStraffic. (Replaceexample.com with your domain name.)

   gcloudcomputessl-certificatescreateCERT_NAME\--domains=example.com

   ReplaceCERT_NAME with the name you want the managed SSL certificate to have (e.g.myservice-cert).

5. Create a target HTTPS proxy.

   gcloudcomputetarget-https-proxiescreateHTTPS_PROXY_NAME\--ssl-certificates=CERT_NAME\--url-map=URLMAP_NAME

   ReplaceHTTPS_PROXY_NAME with the name you want to give to the target HTTPS proxy (e.g.myservice-https).

6. Create a forwarding rule connecting the networking resources you createdto the IP address.

   gcloudcomputeforwarding-rulescreate--globalFORWARDING_RULE_NAME\--target-https-proxy=HTTPS_PROXY_NAME\--address=SERVICE_IP\--ports=443\--load-balancing-scheme=EXTERNAL_MANAGED

   ReplaceFORWARDING_RULE_NAME with the name of the forwarding rule resource you want to create. For example,myservice-lb.

Terraform

Alternatively to the steps described in this section, you can use theGlobal HTTP Load Balancer Terraform Module.

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

1. Configure the IP address:

   resource"google_compute_global_address""lb_default"{provider=google-betaname="myservice-service-ip"  # Use an explicit depends_on clause to wait until API is enableddepends_on=[google_project_service.compute_api]}output"load_balancer_ip_addr"{value=google_compute_global_address.lb_default.address}

   Configures your IP address resource name to bemyservice-service-ip. You can change this to your own value. This IP address is a global anycast IPv4 address that routes to the Google data center or point of presence closest to your visitors.

2. Create and configure the backend service:

   resource"google_compute_backend_service""lb_default"{provider=google-betaname="myservice-backend"load_balancing_scheme="EXTERNAL_MANAGED"backend{group=google_compute_region_network_endpoint_group.lb_default[0].id}backend{group=google_compute_region_network_endpoint_group.lb_default[1].id}  # Use an explicit depends_on clause to wait until API is enableddepends_on=[google_project_service.compute_api,]}

   This resource configures the backend service to be namedmyservice-backend. You can change this to your own value.

3. Configure the URL map:

   resource"google_compute_url_map""lb_default"{provider=google-betaname="myservice-lb-urlmap"default_service=google_compute_backend_service.lb_default.idpath_matcher{name="allpaths"default_service=google_compute_backend_service.lb_default.idroute_rules{priority=1url_redirect{https_redirect=trueredirect_response_code="MOVED_PERMANENTLY_DEFAULT"}}}}

   Connects the backend service resource (myservice-backend) to the new URL map resource (myservice-lb-urlmap). You can change these to your own values.

4. Create a managed TLS certificate for your domain to serve HTTPS traffic. Replaceexample.com with your domain name in thegoogle_compute_managed_ssl_certificate resource:

   resource"google_compute_managed_ssl_certificate""lb_default"{provider=google-betaname="myservice-ssl-cert"managed{domains=["example.com"]}}

5. Configure the HTTPS proxy:

   resource"google_compute_target_https_proxy""lb_default"{provider=google-betaname="myservice-https-proxy"url_map=google_compute_url_map.lb_default.idssl_certificates=[google_compute_managed_ssl_certificate.lb_default.name]depends_on=[google_compute_managed_ssl_certificate.lb_default]}

   Createsgoogle_compute_target_https_proxy resource with target namemyservice-https-proxy and connects previously created TLS certificate (myservice-ssl-cert) and URL mapping resources (myservice-lb-urlmap). You can change these to your own values.

6. Configure the forwarding rule:

   resource"google_compute_global_forwarding_rule""lb_default"{provider=google-betaname="myservice-lb-fr"load_balancing_scheme="EXTERNAL_MANAGED"target=google_compute_target_https_proxy.lb_default.idip_address=google_compute_global_address.lb_default.idport_range="443"depends_on=[google_compute_target_https_proxy.lb_default]}

   Createsgoogle_compute_global_forwarding_rule resource with target namemyservice-https-proxy and connects previously created HTTPS proxy target (myservice-https-proxy) and IP address resource (myservice-service-ip). You can change these to your own values.

7. Apply this config:

   To apply your Terraform configuration in a Google Cloud project, complete the steps in the following sections.

   Prepare Cloud Shell

   1. LaunchCloud Shell.

   2. Set the default Google Cloud project where you want to apply your Terraform configurations.

      You only need to run this command once per project, and you can run it in any directory.

      export GOOGLE_CLOUD_PROJECT=PROJECT_ID

      Environment variables are overridden if you set explicit values in the Terraform configuration file.

   Prepare the directory

   Each Terraform configuration file must have its own directory (alsocalled aroot module).

   1. InCloud Shell, create a directory and a new file within that directory. The filename must have the.tf extension—for examplemain.tf. In this tutorial, the file is referred to asmain.tf.

      mkdirDIRECTORY && cdDIRECTORY && touch main.tf

   2. If you are following a tutorial, you can copy the sample code in each section or step.

      Copy the sample code into the newly createdmain.tf.

      Optionally, copy the code from GitHub. This is recommended when the Terraform snippet is part of an end-to-end solution.

   3. Review and modify the sample parameters to apply to your environment.
   4. Save your changes.
   5. Initialize Terraform. You only need to do this once per directory.

      terraform init

      Optionally, to use the latest Google provider version, include the-upgrade option:

      terraform init -upgrade

   Apply the changes

   1. Review the configuration and verify that the resources that Terraform is going to create or update match your expectations:

      terraform plan

      Make corrections to the configuration as necessary.

   2. Apply the Terraform configuration by running the following command and enteringyes at the prompt:

      terraform apply

      Wait until Terraform displays the "Apply complete!" message.

   3. Open your Google Cloud project to view the results. In the Google Cloud console, navigate to your resources in the UI to make sure that Terraform has created or updated them.
   Note: Terraform samples typically assume that the required APIs are enabled in your Google Cloud project.

gcloud CLI

1. Create a network endpoint group for the Cloud Run service inREGION:

   gcloudcomputenetwork-endpoint-groupscreateNEG_NAME\--region=REGION\--network-endpoint-type=serverless\--cloud-run-service=SERVICE_NAME

   Replace the following:

   • NEG_NAME with the name of the network endpoint group resource. (for example,myservice-neg-uscentral1)
   • REGION with the region your service is deployed in.
   • SERVICE_NAME with the name of your service.

2. Add the network endpoint group to the backend service:

   gcloudcomputebackend-servicesadd-backend--globalBACKEND_NAME\--network-endpoint-group-region=REGION\--network-endpoint-group=NEG_NAME

   Specify theNEG_NAME you created in the previous step for the region.

3. Repeat the preceding steps for each region.

Terraform

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

1. Configure a network endpoint group with namemyservice-neg for the Cloud Run service for each region specified inrun_regions variable:

   resource"google_compute_region_network_endpoint_group""lb_default"{provider=google-betacount=length(local.run_regions)name="myservice-neg"network_endpoint_type="SERVERLESS"region=local.run_regions[count.index]cloud_run{service=google_cloud_run_v2_service.run_default[count.index].name}}

2. Configure a backend service to attach the network endpoint group (myservice-neg):

   resource"google_compute_backend_service""lb_default"{provider=google-betaname="myservice-backend"load_balancing_scheme="EXTERNAL_MANAGED"backend{group=google_compute_region_network_endpoint_group.lb_default[0].id}backend{group=google_compute_region_network_endpoint_group.lb_default[1].id}  # Use an explicit depends_on clause to wait until API is enableddepends_on=[google_project_service.compute_api,]}

gcloud CLI

1. Create a URL map with a redirect rule.

   gcloudcomputeurl-mapsimportHTTP_URLMAP_NAME\--global\--source/dev/stdin<<EOFname:HTTP_URLMAP_NAMEdefaultUrlRedirect:redirectResponseCode:MOVED_PERMANENTLY_DEFAULThttpsRedirect:TrueEOF

   Replace theHTTP_URLMAP_NAME with the name of the URL map resource you will create (for example,myservice-httpredirect).

2. Create a target HTTP proxy with the URL map.

   gcloudcomputetarget-http-proxiescreateHTTP_PROXY_NAME\--url-map=HTTP_URLMAP_NAME

   ReplaceHTTP_PROXY_NAME with the name of the target HTTP proxy you will create (for example,myservice-http).

3. Create a forwarding rule on port80 with the same reserved IP address.

   gcloudcomputeforwarding-rulescreate--globalHTTP_FORWARDING_RULE_NAME\--target-http-proxy=HTTP_PROXY_NAME\--address=SERVICE_IP\--ports=80

   ReplaceHTTP_FORWARDING_RULE_NAME with the name of the new forwarding rule you will create (for example,myservice-httplb).

Terraform

To learn how to apply or remove a Terraform configuration, seeBasic Terraform commands.

1. Create a URL map resource with a redirect rule:

   resource"google_compute_url_map""https_default"{provider=google-betaname="myservice-https-urlmap"default_url_redirect{redirect_response_code="MOVED_PERMANENTLY_DEFAULT"https_redirect=truestrip_query=false}}

2. Create a target HTTP proxy with the newly created URL map resource (myservice-https-urlmap):

   resource"google_compute_target_http_proxy""https_default"{provider=google-betaname="myservice-http-proxy"url_map=google_compute_url_map.https_default.iddepends_on=[google_compute_url_map.https_default]}

3. Create a forwarding rule on port80 with the same reserved IP address resource (myservice-http-proxy):

   resource"google_compute_global_forwarding_rule""https_default"{provider=google-betaname="myservice-https-fr"target=google_compute_target_http_proxy.https_default.idip_address=google_compute_global_address.lb_default.idport_range="80"depends_on=[google_compute_target_http_proxy.https_default]}