이제 설정이 모두 완료되었으므로 서비스를 Cloud Run에 배포하고 서비스 라이브 상태를 확인할 수 있습니다.
실행 구성 정의
서비스를 배포하기 전에 실행 구성을 만들어야 합니다.
탐색 메뉴에서 실행/디버그 구성 선택기로 이동하고 구성 수정을 클릭합니다.
왼쪽 창에서 Cloud Run: 배포를 클릭합니다.
Google Cloud 프로젝트 ID를 설정합니다.
배포 플랫폼에서 Cloud Run 또는 Knative serving 중 플랫폼 환경설정을 선택합니다. 각 옵션에 대한 자세한 설명은 Cloud Run 플랫폼 가이드를 참조하세요.
Cloud Run을 선택한 경우 배포할 리전을 선택합니다.
Knative serving을 선택한 경우 Kubernetes 클러스터 정보를 구성합니다.
서비스가 공개 API 또는 웹사이트인 경우 인증 섹션에서 인증되지 않은 호출 허용을 선택합니다. 그렇지 않으면 인증 필요를 선택합니다.
버전 설정에서 Cloud Code는 컨테이너 이미지 URL 필드를 컨테이너 이미지의 스토리지 위치(서비스가 빌드되고 컨테이너화되면 서비스를 저장하는 위치)로 자동으로 채웁니다.
이 값은 Google Cloud 프로젝트 및 서비스 이름을 기반으로 합니다.
필요한 경우 이 값을 재정의할 수 있습니다.
Cloud Run과 Knative serving 모두 이미지를 다음 중 하나에 저장할 수 있습니다.
Artifact Registry(REGION-docker.pkg.dev/PROJECT_ID/REPO_NAME/IMAGE_PATH 형식 사용)
REGION은 저장소에서 지원되는 리전입니다.
PROJECT_ID는 클러스터가 포함된 Google Cloud 프로젝트의 ID입니다.
REPO_NAME은 이미지가 저장된 저장소의 이름입니다.
IMAGE_PATH는 이미지의 경로입니다.
Container Registry(gcr.io/PROJECT_ID/IMAGE_NAME 형식 사용)
PROJECT_ID는 Google Cloud 프로젝트의 ID입니다.
IMAGE_NAME은 컨테이너 이미지 저장소를 나타냅니다.
Knative serving을 사용하는 경우 docker.io/ACCOUNT 형식을 사용하여 Docker Hub에 이미지를 저장할 수 있습니다. 여기서 ACCOUNT는 Docker Hub 계정의 이름입니다. 비공개 Docker Hub 저장소를 사용하는 경우 올바르게 인증되었는지 확인합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(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)."]]
실행을 클릭합니다.