When you set environment variables, they are injected into the container and are accessible to your code. Environment variables are set as key/value pairs.
The environment variables defined in the container runtime contract
are reserved and cannot be set. In particular, the
PORT environment variable
is injected inside your container by Cloud Run. You should not set it
Setting environment variables on a service
Any configuration change leads to the creation of a new revision. Subsequent revisions will also automatically get this configuration setting unless you make explicit updates to change it.
Click Create Service if you are configuring a new service you are deploying to. If you are configuring an existing service, click on the service, then click Edit and Deploy New Revision.
If you are configuring a new service, fill out the initial service settings page as desired, then click Next > Advanced settings to reach the service configuration page.
Click the Variables & Secrets tab.
Do the following:
- If you are adding a variable, click Add Variable, and specify the name you want for the variable and its value in the Name and Value text boxes.
- If you are changing a value for a variable, replace the current value in the Value text box with the one you want.
- If you are removing one or more environment variables, hover your cursor to the left of the Value textbox of the variable you are removing to display the Trash icon, and click it.
Click Create or Deploy.
To set, update, or remove environment variables of an existing service, use the gcloud run services update command. You can use any of the following flags, as needed:
gcloud run deploy [SERVICE] --image IMAGE_URL --update-env-vars KEY1=VALUE1,KEY2=VALUE2 gcloud run services update SERVICE --update-env-vars KEY1=VALUE1,KEY2=VALUE2
- Replace SERVICE with the name of your service.
- Replace KEY1=VALUE1,KEY2=VALUE2, with the comma separated list of desired variable names and their values.
IMAGE_URLwith a reference to the container image, for example,
If you have too many environment variables that cannot be easily listed in
KEY1=VALUE1,KEY2=VALUE2 format, you can alternatively repeat the flags
listed above multiple times:
[...] --set-env-vars "KEY1=VALUE1" \ --set-env-vars "KEY2=VALUE2" \ --set-env-vars "KEY3=VALUE3"
Because the comma character
, is used to split environment variables, if
your environment variable contains comma characters as values, you need to
escape those delimiters by
specifying a different delimiter character, for example,
You can download and view existing service configuration using the
gcloud run services describe --format export command, which yields
cleaned results in YAML format. You can then modify the fields described below and
upload the modified YAML using the
gcloud run services replace command.
Make sure you only modify fields as documented.
To view and download the configuration:
gcloud run services describe SERVICE --format export > service.yaml
valueattributes under the
apiVersion: serving.knative.dev/v1 kind: Service metadata: name: SERVICE spec: template: spec: containers: - env: - name: KEY-1 value: VALUE-1 - name: KEY-N value: VALUE-N
- SERVICE with the name of your Cloud Run service
- KEY-1, VALUE-1 with the environment variable and value. Optionally add more variables and values as desired.
Replace the service with its new configuration using the following command:
gcloud run services replace service.yaml
Setting default environment variables in the container
You can use the
statement in a Dockerfile to set default values for environment variables:
Order of precedence: container vs service variables
Viewing environment variables settings
To view the current environment variables settings for your service:
Click the service you are interested in to open the Service details page.
Click the Revisions tab.
In the details panel at the right, the environment variables setting is listed under the Variables & Secrets tab.
Use the following command:
gcloud run services describe SERVICE
Locate the environment variables setting in the returned configuration.
For code sample that show how to access environment variables in your code, refer to Handling sensitive configuration with Secret Manager in the End user authentication tutorial.