참고: 표준 서비스는 Cloud Service Mesh 버전 1.6.8 이상에서 자동으로 지원됩니다.
표준 서비스 컨트롤러는 동일한 논리 서비스에 속하는 워크로드를 그룹화하며 Google Cloud 콘솔에서 서비스 대시보드의 전체 기능을 위해 필요합니다.
버전 1.25부터 asmcli로 설치된 모든 관리형 Cloud Service Mesh 설치 및 클러스터 내 설치는 관리형 표준 서비스 컨트롤러를 통해 프로비저닝됩니다. 클러스터 내 표준 서비스 컨트롤러가 지원 중단되었으며 더 이상 업데이트되지 않습니다. 클러스터 내 컨트롤러의 기존 배포는 계속 작동하지만 향후 출시와의 호환성, 최신 기능 액세스, 지속적인 지원을 보장하려면 관리형 표준 서비스 컨트롤러로 마이그레이션하는 것이 좋습니다.
클러스터에서 클러스터 내 표준 서비스 컨트롤러가 사용 설정되어 있는지 확인하려면 다음 안내를 따르세요.
kubectlgetservices-nasm-system
클러스터 내 표준 서비스 컨트롤러 사용 중지
기존 클러스터 내 컨트롤러 배포의 경우 관리형 표준 서비스 컨트롤러로 마이그레이션해야 합니다. 마이그레이션 가이드를 따르세요.
관리형 표준 서비스 컨트롤러 사용 설정
관리형 Cloud Service Mesh를 설치한 경우 관리형 표준 서비스 컨트롤러가 기본적으로 설치됩니다. 또한 버전 1.25부터 asmcli를 사용하는 모든 클러스터 내 Cloud Service Mesh 설치는 관리형 표준 서비스 컨트롤러를 통해 프로비저닝됩니다.
다음 명령어를 실행하여 관리형 표준 서비스 컨트롤러를 실행 중인지 확인합니다.
FLEET_PROJECT_ID를 Fleet 호스트 프로젝트의 ID로 바꿉니다. 일반적으로 FLEET_PROJECT_ID는 프로젝트와 이름이 동일합니다.
설명에 표준 서비스가 성공적으로 조정되었다고 표시되면 관리형 표준 서비스 컨트롤러가 예상대로 작동하는 것입니다. 추가 조치는 필요하지 않습니다.
projects/<your project number>/locations/<location>/memberships/<membership-name>:
code: OK
description: |-
Revision(s) ready for use: asm-managed.
All Canonical Services have been reconciled successfully.
servicemeshFeatureState: {}
updateTime: '2021-11-16T21:10:36.289467777Z'
설명에 관리형 표준 서비스 컨트롤러 대신 클러스터 내 컨트롤러가 사용된다고 표시되면 마이그레이션 가이드를 따르세요.
projects/<your project number>/locations/<location>/memberships/<membership-name>:
code: OK
description: |-
Revision(s) ready for use: istiod-asm-173-6.
The Managed Canonical Service Controller is yielding to the in-cluster controller. See https://cloud.google.com/service-mesh/v1.25/docs/canonical-service-controller-enable-and-disable#disable-in-cluster-service-controller for instructions on removing the in-cluster controller.
servicemeshFeatureState: {}
updateTime: '2021-11-16T21:05:43.286828851Z'
lifecycleState: ENABLED
[[["이해하기 쉬움","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)"],[],[],null,["# Enabling and disabling the Canonical Service controller\n=======================================================\n\n\n**Note:** Canonical Services are supported automatically in Cloud Service Mesh version 1.6.8 and higher.\n\nThe Canonical Service controller groups workloads belonging to the same logical\nservice and is required for the full functionality of the Services dashboard\nin the Google Cloud console.\n\nAll managed Cloud Service Mesh installations and in-cluster installations\nwith asmcli from version 1.25 provisioned with the managed Canonical Service\ncontroller. The in-cluster Canonical Service Controller has been deprecated and\nwill no longer receive updates. While existing deployments of in-cluster\ncontroller will continue to operate, we strongly recommend migrating to the\nmanaged Canonical Service Controller to ensure compatibility with future\nreleases, access to the latest features, and continued support.\n\nTo determine if the in-cluster Canonical Service controller is enabled on your\ncluster: \n\n kubectl get services -n asm-system\n\nDisable the in-cluster Canonical Service controller\n---------------------------------------------------\n\nFor existing in-cluster controller deployments, you should migrate to the managed\nCanonical Service controller. Follow the\n[migration guide](/service-mesh/v1.25/docs/canonical-service-migrate-from-in-cluster-controller).\n\nEnable the Managed Canonical Service Controller\n-----------------------------------------------\n\nIf you installed managed Cloud Service Mesh, then the Managed Canonical\nService Controller was installed by default. Also, all the in-cluster\nCloud Service Mesh installations with asmcli from version 1.25 will be\nprovisioned with the managed Canonical Service controller.\n\nEnsure you are running the Managed Canonical Service Controller by running\nthe following command:\n\nReplace FLEET_PROJECT_ID with the ID of your Fleet Host project. Generally,\nthe FLEET_PROJECT_ID has the same name as the project. \n\n gcloud beta container hub mesh describe --project FLEET_PROJECT_ID\n\n1. If the description states that the Canonical Services are reconciled\n successfully, then Manged Canonical Service Controller is operating as\n expected. No further action is required.\n\n projects/\u003cyour project number\u003e/locations/\u003clocation\u003e/memberships/\u003cmembership-name\u003e:\n code: OK\n description: |-\n Revision(s) ready for use: asm-managed.\n All Canonical Services have been reconciled successfully.\n servicemeshFeatureState: {}\n updateTime: '2021-11-16T21:10:36.289467777Z'\n\n2. If the description states that Managed Canonical Service Controller is\n yielding to the in-cluster controller, follow the [migration guide](/service-mesh/v1.25/docs/canonical-service-migrate-from-in-cluster-controller).\n\n projects/\u003cyour project number\u003e/locations/\u003clocation\u003e/memberships/\u003cmembership-name\u003e:\n code: OK\n description: |-\n Revision(s) ready for use: istiod-asm-173-6.\n The Managed Canonical Service Controller is yielding to the in-cluster controller. See https://cloud.google.com/service-mesh/v1.25/docs/canonical-service-controller-enable-and-disable#disable-in-cluster-service-controller for instructions on removing the in-cluster controller.\n servicemeshFeatureState: {}\n updateTime: '2021-11-16T21:05:43.286828851Z'\n lifecycleState: ENABLED\n\n3. For any other issues, refer to [Resolve Managed Canonical Service Controller issues](/service-mesh/v1.25/docs/troubleshooting/troubleshoot-canonical-service#resolve-managed-canonical-controller-issues) for\n troubleshooting guidance.\n\nWhat's next\n-----------\n\nLearn about:\n\n- [Canonical Services](/service-mesh/v1.25/docs/canonical-service)\n- [Best practices in Canonical Services](/service-mesh/v1.25/docs/canonical-service-best-practices)\n- [Define a Canonical Service](/service-mesh/v1.25/docs/define-canonical-service)\n- [Resolving Canonical Service issues](/service-mesh/v1.25/docs/troubleshooting/troubleshoot-canonical-service)"]]
