Deploy a service to Cloud Run in Cloud Code for IntelliJ
Stay organized with collections
Save and categorize content based on your preferences.
Now that you're all set up, you can deploy your service to
Cloud Run and view your service live.
Defining your run configuration
Before you deploy your service, you must create your run configuration:
Navigate to Run/Debug configurations selector in the Navigation bar and click
Edit Configurations.
In the left pane, click Cloud Run: Deploy.
Set your Google Cloud project ID.
Choose your platform preferences under Deployment Platform,
either Cloud Run or Knative serving. For
a detailed description of each option, see the
Cloud Run platform guide.
If Cloud Run is selected, choose a region to
deploy to.
If Knative serving is selected, configure the Kubernetes
cluster information.
If your service is a public API or website, choose Allow unauthenticated
invocations in the Authentication section. Otherwise, select
Require authentication.
Under Revision Settings, Cloud Code automatically populates the
container image URL field with the storage location of your container
image (where it stores your service, once it builds and containerizes it).
This value is based on your Google Cloud project and service name.
If you need to, you can override this value:
For both Cloud Run and
Knative serving, you can store your images on either:
Artifact Registry, using the format
REGION-docker.pkg.dev/PROJECT_ID/REPO_NAME/IMAGE_PATH
REGION is the repository's supported region
PROJECT_ID is the ID of your Google Cloud project
containing your cluster
REPO_NAME is the name of your repository where your image is stored
IMAGE_PATH is the path to your image
Container Registry, using the format
gcr.io/PROJECT_ID/IMAGE_NAME
PROJECT_ID is the ID of your Google Cloud project
IMAGE_NAME refers to the container image repository
If you're using Knative serving, you can store
your images on Docker Hub using the format,
docker.io/ACCOUNT, where ACCOUNT is the name of your Docker Hub
account. Make sure that you're
properly authenticated
if you're using a private Docker Hub repository.
Under Build settings, choose whether to build locally or on
Cloud Build.
Choose a builder and plugin.
Cloud Code supports Docker, Jib, and Buildpacks
artifact types.
Click OK.
Optional: Customizing your configuration
When deploying your service, you can specify additional settings such as
a service account, environment variables, and, when using
Cloud Run, a VPC Connector and SQL connections. Specify
the additional settings in the Advanced revision settings section when you
choose Edit Configurations.
Environment variables:
The following environment variables are automatically added to the running
containers:
Name
Description
Example
PORT
The port your HTTP server should listen on.
8080
K_SERVICE
The name of the Cloud Run service being run.
hello-world
K_REVISION
The name of the Cloud Run revision being run.
hello-world.1
K_CONFIGURATION
The name of the Cloud Run configuration that created the revision.
hello-world
Deploying your service
To deploy your service, follow these steps:
Choose your run target from the Run/Debug configurations dialog on the top
taskbar.
Click Run.
View your running service by following the URL displayed in
the output window.
You can also view the status of your service (metrics, revision details,
and more) by following the logs URL displayed in the output window.
Get support
To submit feedback or report an issue in your IntelliJ IDE, go to
Tools > Cloud Code > Help / About > Submit
feedback or report an issue to report an issue on GitHub.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eBefore deploying, configure your run settings by navigating to the "Edit Configurations" section under the Run/Debug selector.\u003c/p\u003e\n"],["\u003cp\u003eChoose your deployment platform, selecting either Cloud Run or Knative serving, and configure settings such as region or Kubernetes cluster details.\u003c/p\u003e\n"],["\u003cp\u003eSpecify whether your service requires authentication or allows unauthenticated invocations for public access.\u003c/p\u003e\n"],["\u003cp\u003eConfigure your container image storage location, choosing between Artifact Registry, Container Registry, or Docker Hub, based on your needs.\u003c/p\u003e\n"],["\u003cp\u003eAfter configuring the run settings, you can deploy the service by clicking "Run," and then access the live service and its status via the URLs in the output window.\u003c/p\u003e\n"]]],[],null,["# Deploy a service to Cloud Run in Cloud Code for IntelliJ\n\nNow that you're all set up, you can deploy your service to\nCloud Run and view your service live.\n\nDefining your run configuration\n-------------------------------\n\nBefore you deploy your service, you must create your run configuration:\n\n1. Navigate to Run/Debug configurations selector in the Navigation bar and click **Edit Configurations**.\n2. In the left pane, click **Cloud Run: Deploy**.\n3. Set your Google Cloud project ID.\n4. Choose your platform preferences under **Deployment Platform** ,\n either **Cloud Run** or **Knative serving** . For\n a detailed description of each option, see the\n [Cloud Run platform guide](/run/docs/choosing-a-platform).\n\n - If **Cloud Run** is selected, choose a region to deploy to.\n - If **Knative serving** is selected, configure the Kubernetes\n cluster information.\n\n5. If your service is a public API or website, choose **Allow unauthenticated\n invocations** in the Authentication section. Otherwise, select\n **Require authentication**.\n\n6. Under Revision Settings, Cloud Code automatically populates the\n container image URL field with the storage location of your container\n image (where it stores your service, once it builds and containerizes it).\n This value is based on your Google Cloud project and service name.\n\n If you need to, you can override this value:\n - For both Cloud Run and Knative serving, you can store your images on either:\n - [Artifact Registry](/artifact-registry/docs), using the format **\u003cvar class=\"readonly\" translate=\"no\"\u003eREGION\u003c/var\u003e-docker.pkg.dev/\u003cvar class=\"readonly\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/\u003cvar class=\"readonly\" translate=\"no\"\u003eREPO_NAME\u003c/var\u003e/\u003cvar class=\"readonly\" translate=\"no\"\u003eIMAGE_PATH\u003c/var\u003e**\n - \u003cvar class=\"readonly\" translate=\"no\"\u003eREGION\u003c/var\u003e is the repository's supported region\n - \u003cvar class=\"readonly\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is the ID of your Google Cloud project containing your cluster\n - \u003cvar class=\"readonly\" translate=\"no\"\u003eREPO_NAME\u003c/var\u003e is the name of your repository where your image is stored\n - \u003cvar class=\"readonly\" translate=\"no\"\u003eIMAGE_PATH\u003c/var\u003e is the path to your image\n\n | **Note:** Consider [transitioning from Container Registry](/artifact-registry/docs/transition/transition-from-gcr) since Artifact Registry is the recommended service for managing container images. [Container Registry](/container-registry/docs) is still supported but will only receive critical security fixes.\n - Container Registry, using the format **gcr.io/\u003cvar class=\"readonly\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e/\u003cvar class=\"readonly\" translate=\"no\"\u003eIMAGE_NAME\u003c/var\u003e**\n - \u003cvar class=\"readonly\" translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e is the ID of your Google Cloud project\n - \u003cvar class=\"readonly\" translate=\"no\"\u003eIMAGE_NAME\u003c/var\u003e refers to the container image repository\n - If you're using Knative serving, you can store\n your images on Docker Hub using the format,\n **docker.io/\u003cvar class=\"readonly\" translate=\"no\"\u003eACCOUNT\u003c/var\u003e** , where \u003cvar class=\"readonly\" translate=\"no\"\u003eACCOUNT\u003c/var\u003e is the name of your Docker Hub\n account. Make sure that you're\n [properly authenticated](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry)\n if you're using a private Docker Hub repository.\n\n7. Under Build settings, choose whether to build locally or on\n Cloud Build.\n\n8. Choose a builder and plugin.\n\n Cloud Code supports Docker, Jib, and Buildpacks\n [artifact types](https://skaffold.dev/docs/builders/).\n9. Click **OK**.\n\n### Optional: Customizing your configuration\n\nWhen deploying your service, you can specify additional settings such as\na service account, environment variables, and, when using\nCloud Run, a VPC Connector and SQL connections. Specify\nthe additional settings in the **Advanced revision settings** section when you\nchoose **Edit Configurations**.\n\n**Environment variables:**\n\nThe following environment variables are automatically added to the running\ncontainers:\n\nDeploying your service\n----------------------\n\nTo deploy your service, follow these steps:\n\n1. Choose your run target from the Run/Debug configurations dialog on the top taskbar.\n2. Click **Run**.\n3. View your running service by following the URL displayed in the **output window**.\n4. You can also view the status of your service (metrics, revision details,\n and more) by following the logs URL displayed in the output window.\n\nGet support\n-----------\n\nTo submit feedback or report an issue in your IntelliJ IDE, go to **Tools** \\\u003e **Cloud Code** \\\u003e **Help / About** \\\u003e **Submit\nfeedback or report an issue** to report an issue on [GitHub](https://github.com/GoogleCloudPlatform/cloud-code-intellij/issues)."]]