Cloud Service Mesh dan Traffic Director kini bergabung menjadi Cloud Service Mesh. Untuk mengetahui informasi selengkapnya, lihat ringkasan Cloud Service Mesh.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mengaktifkan dan menonaktifkan pengontrol Layanan Kanonik
Catatan: Layanan Kanonik didukung secara otomatis di Cloud Service Mesh versi 1.6.8 dan yang lebih baru.
Pengontrol Layanan Kanonik mengelompokkan beban kerja yang termasuk dalam layanan logika yang sama dan diperlukan untuk fungsi penuh dasbor Layanan di konsol Google Cloud .
Semua penginstalan Cloud Service Mesh terkelola dan penginstalan dalam cluster
dengan asmcli dari versi 1.25 yang disediakan dengan pengontrol Layanan Kanonik
terkelola. Pengontrol Layanan Kanonik dalam cluster tidak digunakan lagi dan
tidak akan lagi menerima update. Meskipun deployment pengontrol dalam cluster yang ada
akan terus beroperasi, sebaiknya migrasikan ke
Pengontrol Layanan Canonical terkelola untuk memastikan kompatibilitas dengan rilis
mendatang, akses ke fitur terbaru, dan dukungan berkelanjutan.
Untuk menentukan apakah pengontrol Layanan Kanonik dalam cluster diaktifkan di cluster Anda:
kubectlgetservices-nasm-system
Menonaktifkan pengontrol Layanan Kanonik dalam cluster
Untuk deployment pengontrol dalam cluster yang ada, Anda harus bermigrasi ke pengontrol
Layanan Kanonik terkelola. Ikuti
panduan migrasi.
Mengaktifkan Pengontrol Layanan Kanonik Terkelola
Jika Anda menginstal Cloud Service Mesh terkelola, Managed Canonical Service Controller akan diinstal secara default. Selain itu, semua penginstalan Cloud Service Mesh dalam cluster dengan asmcli dari versi 1.25 akan disediakan dengan pengontrol Layanan Kanonik terkelola.
Pastikan Anda menjalankan Pengontrol Layanan Kanonik Terkelola dengan menjalankan perintah berikut:
Ganti FLEET_PROJECT_ID dengan ID project Host Flotte Anda. Umumnya, FLEET_PROJECT_ID memiliki nama yang sama dengan project.
Jika deskripsi menyatakan bahwa Layanan Kanonik berhasil
direkonsiliasi, Pengontrol Layanan Kanonik Terkelola beroperasi seperti
yang diharapkan. Tidak diperlukan tindakan lebih lanjut.
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'
Jika deskripsi menyatakan bahwa Pengontrol Layanan Kanonik Terkelola
menghasilkan pengontrol dalam cluster, ikuti panduan migrasi.
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/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
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 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/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/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/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/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/docs/canonical-service)\n- [Best practices in Canonical Services](/service-mesh/docs/canonical-service-best-practices)\n- [Define a Canonical Service](/service-mesh/docs/define-canonical-service)\n- [Resolving Canonical Service issues](/service-mesh/docs/troubleshooting/troubleshoot-canonical-service)"]]
