모든 관리자 클러스터는 Fleet에 등록해야 합니다.
관리자 클러스터에서 관리하는 모든 사용자 클러스터는 관리자 클러스터와 동일한 Fleet에 등록해야 합니다.
관리자 또는 사용자 클러스터가 Fleet에 등록되면 Fleet 호스트 프로젝트와 연결됩니다. 관리자 클러스터와 이 클러스터가 관리하는 모든 사용자 클러스터에는 동일한 Fleet 호스트 프로젝트가 있습니다. Google Cloud 콘솔의 Fleet 호스트 프로젝트에서 관리자 클러스터와 사용자 클러스터를 보고 관리할 수 있습니다.
Fleet 호스트 프로젝트로 제공할 Google Cloud 프로젝트를 선택합니다. 기존 프로젝트를 선택하거나 새 프로젝트를 만들 수 있습니다. 프로젝트 ID를 기록해 둡니다. 다음 단계에서는 Fleet 호스트 프로젝트의 ID가 필요합니다.
gcloud container vmware clusters create를 호출할 때 --project 값을 제공합니다.
구성요소 액세스 서비스 계정의 상위 프로젝트
클러스터를 만들기 전에 Google Distributed Cloud가 Artifact Registry에서 구성요소를 다운로드하는 데 사용할 수 있는 서비스 계정이 있어야 합니다.
이 서비스 계정을 구성요소 액세스 서비스 계정이라고 합니다.
구성요소 액세스 서비스 계정을 만든 Google Cloud 프로젝트를 구성요소 액세스 서비스 계정의 상위라고 합니다. 이 프로젝트는 Fleet 호스트 프로젝트와 동일하거나 다를 수 있습니다. 서비스 계정과 상위 프로젝트에 대한 자세한 내용은 서비스 계정 및 Google Cloud 프로젝트 이해를 참조하세요.
구성요소 액세스 서비스 계정의 상위 프로젝트에 필요한 API를 사용 설정하려면 다음 안내를 따르세요.
[[["이해하기 쉬움","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-01(UTC)"],[],[],null,["This document shows how to associate one or more Google Cloud projects with a\ncluster in Google Distributed Cloud.\n\nThe instructions here are complete. For a shorter introduction to using a\nGoogle Cloud project, see\n[Set up minimal infrastructure](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/minimal-infrastructure).\n\nBefore you begin\n\n[Install Google Cloud CLI](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/cloud-sdk).\n\nFleet host project\n\nEvery admin cluster must be registered to a\n[fleet](/anthos/fleet-management/docs).\nAnd every user cluster managed by an admin cluster must be registered to the\nsame fleet as the admin cluster.\n\nWhen an admin or user cluster is registered to a fleet, it is associated with a\n*fleet host project*. An admin cluster and all the user clusters it manages\nhave the same fleet host project. In the Google Cloud console, in the fleet host\nproject, you can see and manage your admin and user clusters.\n\nChoose a Google Cloud project to serve as your fleet host project. You can choose\nan existing project, or you can create a new one. Make a note of the project\nID. You need the ID of your fleet host project in the steps that follow.\n\nEnable APIs in your fleet host project\n\nIn your fleet host project, enable the required APIs: \n\nLinux and macOS\n\nEnable the following APIs in your fleet host project:\n\n```\ngcloud services enable --project FLEET_HOST_PROJECT_ID \\\n anthos.googleapis.com \\\n container.googleapis.com \\\n gkehub.googleapis.com \\\n gkeconnect.googleapis.com \\\n connectgateway.googleapis.com \\\n monitoring.googleapis.com \\\n kubernetesmetadata.googleapis.com \\\n logging.googleapis.com \\\n opsconfigmonitoring.googleapis.com \\\n serviceusage.googleapis.com \\\n iam.googleapis.com \\\n cloudresourcemanager.googleapis.com\n```\n\nIf you want to manage the lifecycle of clusters in the\nGoogle Cloud console, the Google Cloud CLI, or\n[Terraform](https://www.terraform.io/), enable these\nadditional APIs in your fleet host project:\n\n```\ngcloud services enable --project FLEET_HOST_PROJECT_ID \\\n gkeonprem.googleapis.com \\\n anthosaudit.googleapis.com \\\n storage.googleapis.com\n```\n\nWindows\n\nEnable the following APIs in your fleet host project:\n\n```\ngcloud services enable --project FLEET_HOST_PROJECT_ID ^\n anthos.googleapis.com ^\n container.googleapis.com ^\n gkehub.googleapis.com ^\n gkeconnect.googleapis.com ^\n connectgateway.googleapis.com ^\n monitoring.googleapis.com ^\n kubernetesmetadata.googleapis.com ^\n logging.googleapis.com ^\n opsconfigmonitoring.googleapis.com ^\n serviceusage.googleapis.com ^\n iam.googleapis.com ^\n cloudresourcemanager.googleapis.com\n```\n\nIf you want to manage the lifecycle of user clusters in the\nGoogle Cloud console, the Google Cloud CLI, or\n[Terraform](https://www.terraform.io/), enable these\nadditional APIs in your fleet host project:\n\n```\ngcloud services enable --project FLEET_HOST_PROJECT_ID ^\n gkeonprem.googleapis.com ^\n anthosaudit.googleapis.com ^\n storage.googleapis.com\n```\n\nGrant roles to service accounts on your fleet host project\n\nYour connect-register service account must be granted certain roles on your\nfleet host project. For details see\n[Connect-register service account](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts#connect_register_service_account).\n\nYour logging-monitoring service account must be granted certain roles on your\nfleet host project. For details, see\n[Logging-monitoring service account](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts#logging_monitoring_service_account).\n\nYour audit logging service account must be granted certain roles on your\nfleet host project. For details, see\n[Audit logging service account](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts#audit_logging_service_account).\n\nRegister a cluster to a fleet\n\nYou register a cluster to a fleet when you create the cluster. The details\nof registration depend on what tool you use to create the cluster:\n\n| Tool | How to register |\n|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| `gkectl` | Fill in the [gkeConnect.projectID](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/admin-cluster-configuration-file-latest#gkeconnect-projectid-field) field in the cluster configuration file. |\n| Google Cloud console | The cluster is automatically registered. The Google Cloud project that you use to create the cluster becomes the fleet host project. |\n| Terraform | Fill in the `project_id` field in the [.tfvars file](https://registry.terraform.io/providers/terraform-redhat/rhcs/latest/docs/guides/terraform-vars). |\n| gcloud CLI | When you call `gcloud container vmware clusters create`, provide a value for `--project`. |\n\nParent project of your component access service account\n\nBefore you create a cluster, you must have a service account that\nGoogle Distributed Cloud can use to download components from Artifact Registry.\nThis service account is called your *component access service account*.\n\nThe Google Cloud project where you created your component access service\naccount is called the *parent* of your component access service account. This\nproject can be the same as your fleet host project, or it can be different. For\nmore information about service accounts and parent projects see\n[Understanding service accounts and Google Cloud projects](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts#understanding_service_accounts_and).\n\nTo enable the required APIs for the parent project of your component access\nservice account: \n\nLinux and macOS \n\n```\ngcloud services enable --project [PARENT_PROJECT_ID] \\\n serviceusage.googleapis.com \\\n iam.googleapis.com \\\n cloudresourcemanager.googleapis.com\n```\n\nWindows \n\n```\ngcloud services enable --project [PARENT_PROJECT_ID] ^\n serviceusage.googleapis.com ^\n iam.googleapis.com ^\n cloudresourcemanager.googleapis.com\n```\n\nWhat's next\n\n[Create service accounts and keys](/kubernetes-engine/distributed-cloud/vmware/docs/how-to/service-accounts)."]]
