Console

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

   Go to Cloud Run

2. SelectWorker pools from the menu, and clickDeploy container toconfigure a new worker pool.If you are configuring an existing worker pool, click theworker pool, then clickEdit and deploy new revision.

3. If you are configuring a new worker pool, fill out the initial workerpool page, then clickContainer(s), Volumes, Networking, Security to expand theworker pools configuration page.

4. Click theContainer tab.

   

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

5. ClickCreate orDeploy.

gcloud

Toupdate the start command and arguments for an existing service:

gcloudbetarunworker-poolsupdateWORKER_POOL--commandCOMMAND--argsARG1,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 duringdeployment of a new or existing worker pool:

gcloudbetarunworker-poolsdeploy--imageIMAGE_URL--commandCOMMAND--argsARG1,ARG-N

ReplaceIMAGE_URL with a reference to the container image thatcontains the worker pool, such asus-docker.pkg.dev/cloudrun/container/worker-pool:latest.

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

gcloudbetarunworker-poolsdeploy--imageIMAGE_URL--command""--args""

YAML

1. If you are creating a new worker pool, skip this step.If you are updating an existing worker pool, download itsYAML configuration:

   gcloudbetarunworker-poolsdescribeWORKER_POOL--formatexport>workerpool.yaml

2. The following example contains the YAML configuration:

   apiVersion:run.googleapis.com/v1kind:WorkerPoolmetadata:name:WORKER_POOLannotations:run.googleapis.com/launch-stage:BETAspec:template:spec:containers:-name:CONTAINER_NAMEimage:IMAGE_URLcommand:-COMMANDargs:-ARG1-ARG-N

   Replace the following:

   • WORKER_POOL: the name of your Cloud Run worker pool.
   • CONTAINER_NAME: the name of the container.
   • IMAGE_URL: a reference to the container image thatcontains the worker pool, such asus-docker.pkg.dev/cloudrun/container/worker-pool:latest
   • COMMAND: the command that the container is to start up with if you are not using the default command.
   • ARG1: the argument you are sending to the container command. If you use multiple arguments, specify each on its own line—for example, as shown,ARG-N.

3. Create or update the worker pool using the following command:

   gcloudbetarunworker-poolsreplaceworkerpool.yaml

Terraform

To learn how to apply or remove a Terraform configuration, seeBasic 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 thatcontains the worker pool, such asus-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 thecontainer command.

Console

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

   Go to Cloud Run

   • SelectWorker pools from the menu.
   • For an existing worker pool, click the worker pool in the list and selectEdit and deploy new revision to display the revision deployment form.
   • For a new worker pool, clickDeploy container to display theCreate worker pool form.

2. For a new worker pool, specify the worker pool name, ingress container URL, CPUallocation, ingress control, and authentication. In theContainer(s), Volumes, Networking, Security tab, do the following:

   1. Configure the ingress container.
   2. To add each of the other containers you are deploying, clickAdd container.
   3. For all containers except the ingress container,configure a startup health check.
   4. If a container needs to be started after certain othercontainers, select those containers in theContainer 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 ownContainer startup order menu. If a container needs other containers to startfirst before it can start, use theContainer startup ordermenu to select the containers that must start first.

4. Finish any other required configurations, then clickCreate for a newworker pool orDeploy for 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, aCloud 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:

gcloudbetarunworker-poolsdeployWORKER_POOL\--containerCONTAINER_1_NAME--image='WORKER_POOL_IMAGE'--containerCONTAINER_2_NAME--image='SIDECAR_IMAGE'--depends-on=CONTAINER_1_NAME\--containerCONTAINER_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 thatcontains the worker pool, such asus-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 eachcontainer's configuration after thecontainer parameters.

YAML

1. If you are creating a new worker pool, skip this step.If you are updating an existing worker pool, download itsYAML configuration:

   gcloudbetarunworker-poolsdescribeWORKER_POOL--formatexport>workerpool.yaml

2. The following example contains the YAML configuration:

   apiVersion:run.googleapis.com/v1kind:WorkerPoolmetadata:name:WORKER_POOLannotations:run.googleapis.com/launch-stage:BETAspec:template:metadata:annotations:run.googleapis.com/container-dependencies:'{"CONTAINER1":["CONTAINER2"],"CONTAINER3":["CONTAINER1","CONTAINER2"]}'

   Replace the following:

   • WORKER_POOL: the name of your Cloud Run worker pool.
   • CONTAINER1: the name of the first container thatdepends on one or more container. You can set thecontainer name in the YAML; Cloud Run automaticallygenerates a name if one isn't specified.
   • CONTAINER2: the name of the container that muststart beforeCONTAINER1.
   • CONTAINER3: the name of the second container thatdepends on one or more containers.

   In the example shown in the YAML snippet,CONTAINER2starts first,CONTAINER1 starts second, andCONTAINER3 starts last.

3. Create or update the worker pool using the following command:

   gcloudbetarunworker-poolsreplaceworkerpool.yaml