Configure containers for worker pools

Console

1. In the Google Cloud console, go to Cloud Run:

   Go to Cloud Run

2. Select Worker poolsfrom the menu, and click Deploy containerto configure a new worker pool. If you are configuring an existing worker pool, click the worker pool, then click Edit and deploy new revision.

3. If you are configuring a new worker pool, fill out the initial worker pool page, then click Container(s), Volumes, Networking, Securityto expand the worker pools configuration page.

4. Click the Containertab.

   

   • Specify the command you want the container to run if you don't want to use the entry point command defined in the container image. Optionally, specify the arguments to the entrypoint command.

5. Click Createor Deploy.

gcloud

To update the start command and arguments for an existing service:

gcloud  
beta  
run  
worker-pools  
update  
 WORKER_POOL 
  
--command  
 COMMAND 
  
--args  
 ARG1 
, ARG-N 

Replace the following:

• WORKER_POOL : the name of the worker pool.
• COMMAND : the command that the container starts with, if you are not using the default command.
• ARG1 : the argument you are sending to the container command. Use a comma-delimited list for more than one argument.

To specify entrypoint and arguments during deployment of a new or existing worker pool:

gcloud  
beta  
run  
worker-pools  
deploy  
--image  
 IMAGE_URL 
  
--command  
 COMMAND 
  
--args  
 ARG1 
, ARG-N 

Replace IMAGE_URL with a reference to the container image that contains the worker pool, such as us-docker.pkg.dev/cloudrun/container/worker-pool:latest .

If you want to restore the container defaults for the entrypoint commands and arguments, supply empty strings as follows:

gcloud  
beta  
run  
worker-pools  
deploy  
--image  
 IMAGE_URL 
  
--command  
 "" 
  
--args  
 "" 

Terraform

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

  resource 
  
 "google_cloud_run_v2_worker_pool" 
  
 "default" 
  
 { 
  
 name 
  
 = 
  
 " WORKER_POOL 
" 
  
 location 
  
 = 
  
 " REGION 
" 
  
 launch_stage 
  
 = 
  
 "BETA" 
  
 template 
  
 { 
  
 containers 
  
 { 
  
 image 
  
 = 
  
 " IMAGE_URL 
" 
  
 command 
  
 = 
  
 [ 
 " COMMAND 
" 
 ] 
  
 args 
  
 = 
  
 [ 
 " ARG1 
", " ARG2 
" 
 ] 
  
 } 
  
 } 
 } 
 

Replace the following:

• WORKER_POOL : the name of the worker pool.
• REGION : the Google Cloud region—for example, europe-west1 .
• IMAGE_URL : a reference to the container image that contains the worker pool, such as us-docker.pkg.dev/cloudrun/container/worker-pool:latest .
• COMMAND : the command that the container starts with, if you are not using the default command.
• ARG1 , ARG2 : the argument(s) you are sending to the container command.

Console

1. In the Google Cloud console, go to the Cloud Run page:

   Go to Cloud Run

   • Select Worker poolsfrom the menu.
   • For an existing worker pool, click the worker pool in the list and select Edit and deploy new revisionto display the revision deployment form.
   • For a new worker pool, click Deploy containerto display the Create worker poolform.

2. For a new worker pool, specify the worker pool name, ingress container URL, CPU allocation, ingress control, and authentication. In the Container(s), Volumes, Networking, Securitytab, do the following:

   1. Configure the ingress container.
   2. To add each of the other containers you are deploying, click Add container.
   3. For all containers except the ingress container, configure a startup health check .
   4. If a container needs to be started after certain other containers, select those containers in the Container startup ordermenu.

3. For an existing worker pool, follow these steps:

   1. For all containers except the ingress container, configure a startup health check .
   2. Each container is shown with its own Container startup ordermenu. If a container needs other containers to start first before it can start, use the Container startup ordermenu to select the containers that must start first.

4. Finish any other required configurations, then click Createfor a new worker pool or Deployfor an existing worker pool. Wait for the deployment to finish.

gcloud

Before using the Google Cloud CLI to specify startup order, configure a startup health check .

1. In the Google Cloud console, activate Cloud Shell.

   Activate Cloud Shell

   At the bottom of the Google Cloud console, a Cloud Shell session starts and displays a command-line prompt. Cloud Shell is a shell environment with the Google Cloud CLI already installed and with values already set for your current project. It can take a few seconds for the session to initialize.

2. To deploy multiple containers to a service with a specified startup order, run the command:

gcloud  
beta  
run  
worker-pools  
deploy  
 WORKER_POOL 
  
 \ 
  
--container  
 CONTAINER_1_NAME 
  
--image = 
 ' WORKER_POOL_IMAGE 
' 
  
--container  
 CONTAINER_2_NAME 
  
--image = 
 ' SIDECAR_IMAGE 
' 
  
--depends-on = 
 CONTAINER_1_NAME 
  
 \ 
  
--container  
 CONTAINER_3_NAME 
  
--image = 
 ' SIDECAR_IMAGE 
' 
  
--depends-on = 
 CONTAINER_1_NAME 
, CONTAINER_2_NAME 

Replace the following:

• WORKER_POOL : the name of the worker pool.
• IMAGE_URL : a reference to the container image that contains the worker pool, such as us-docker.pkg.dev/cloudrun/container/worker-pool:latest .

• SIDECAR_IMAGE : a reference to the sidecar container image.

  If you want to configure each container in the deploy command, supply each container's configuration after the container parameters.