Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Habilita e inhabilita el controlador del servicio canónico
Nota: Los servicios canónicos son compatibles de forma automática
en Cloud Service Mesh versión 1.6.8 y versiones posteriores.
Cuando instalas o actualizas Cloud Service Mesh con asmcli, se implementa el
controlador de servicios canónicos
en tu clúster. El controlador de servicios canónicos agrupa las cargas de trabajo que pertenecen al mismo servicio lógico y es necesario para la funcionalidad completa del panel de servicios en la consola de Google Cloud . Implementar el controlador crea la implementación canonical-service-controller-manager en tu clúster en el espacio de nombres asm-system y no afecta tus servicios ni cargas de trabajo.
Si no usaste la herramienta asmcli para instalar Cloud Service Mesh, es posible que no tengas habilitado el controlador del servicio canónico en tu clúster. Para determinar si el controlador del servicio canónico está habilitado en tu clúster, haz lo siguiente:
kubectl get services -n asm-system
Habilita el controlador del servicio canónico en el clúster
Si el controlador del servicio canónico no está habilitado, puedes habilitarlo si realizas los siguientes pasos:
Descarga el paquete kpt que contiene el controlador en el directorio de trabajo actual:
Habilita el controlador del servicio canónico administrado
Si prefieres no instalar el controlador en el clúster, puedes habilitar el controlador de servicio canónico administrado, que realiza la misma función para todos los clústeres registrados en tu malla sin necesidad de instalar o administrar el controlador tú mismo.
El controlador administrado está diseñado para funcionar con el controlador en el clúster.
Si migras desde el controlador dentro del clúster, debes borrar el controlador dentro de cada clúster en el que se ejecuta para que el controlador administrado tome el control. Para obtener más información, consulta Inhabilita el controlador del servicio canónico en el clúster.
Para habilitar el controlador administrado, haz lo siguiente:
Página de funciones de Anthos
En la Google Cloud consola, ve a la página de clústeres de GKE Enterprise.
Haz clic en Habilitar junto a la función “Malla de servicios”.
Después de unos minutos, el controlador administrado se activa y crea servicios canónicos para las cargas de trabajo que se ejecutan en los clústeres registrados en tu malla. Ejecuta kubectl get canonicalservices --all-namespaces a fin de confirmar que se crearon algunos servicios canónicos para las cargas de trabajo en la malla.
La descripción indica que los servicios canónicos se concilian de forma correcta:
projects/<your project number>/locations/global/memberships/<your cluster 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'
Si los servicios canónicos no se concilian de forma correcta, aparecerá un mensaje de error o un resultado similar al mensaje siguiente:
projects/<your project number>/locations/global/memberships/<your cluster 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.20/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
Instalación de plano de control administrado
Si instalaste Cloud Service Mesh administrado (con la API de Fleet o asmcli), el controlador de servicios canónicos administrado se instaló de forma predeterminada.
Asegúrate de ejecutar el controlador del servicio canónico administrado mediante el siguiente comando:
La descripción indica que los servicios canónicos se concilian de forma correcta:
projects/<your project number>/locations/global/memberships/<your cluster 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'
Si los servicios canónicos no se concilian de forma correcta, aparecerá un mensaje de error o un resultado similar al mensaje siguiente:
projects/<your project number>/locations/global/memberships/<your cluster 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.20/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
¿Qué sigue?
Obtén más información acerca de los siguientes temas:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[],[],null,["Enabling and disabling the Canonical Service controller\n\n\n**Note:** Canonical Services are supported automatically in Cloud Service Mesh version 1.6.8 and higher.\n\nWhen you install or upgrade Cloud Service Mesh using the\n[`asmcli`](/service-mesh/v1.20/docs/unified-install/asmcli-overview), it deploys the\n[Canonical Service controller](https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages/blob/master/asm/canonical-service/controller.yaml)\nto your cluster. The Canonical Service controller groups workloads belonging to\nthe same logical service, and is required for the full functionality of\nthe Services dashboard in the Google Cloud console. Deploying the controller\ncreates the `canonical-service-controller-manager` deployment in your cluster in\nthe `asm-system` namespace, and does not affect your services or workloads.\n\nIf you didn't use the `asmcli` tool to install Cloud Service Mesh, you might not have\nthe Canonical Service controller enabled on your cluster. To determine if the\nCanonical Service controller is enabled on your cluster: \n\n kubectl get services -n asm-system\n\nEnable the in-cluster Canonical Service controller\n\nIf the Canonical Service controller isn't enabled, you can enable it with\nthe following steps:\n\n1. Download the `kpt` package that contains the controller to the current working\n directory:\n\n kpt pkg get https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages.git/asm@release-1.25 asm\n\n2. Apply the controller configuration:\n\n kubectl apply -f asm/canonical-service/controller.yaml\n\nDisable the in-cluster Canonical Service controller\n\nIf you want to disable the Canonical Service controller:\n\n1. Download the kpt package that contains the controller to the current working\n directory:\n\n kpt pkg get https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages.git/asm@release-1.25 asm\n\n2. Delete the controller from your cluster:\n\n kubectl delete -f asm/canonical-service/controller.yaml\n\nEnable the Managed Canonical Service Controller **Platform note:** Managed Canonical Service Controller is not supported on Google Distributed Cloud (includes Google Distributed Cloud and Google Distributed Cloud).\n\nIf you would prefer not to install the in-cluster controller, you can instead\nenable the Managed Canonical Service Controller, which performs the same\nfunction for all the registered clusters in your mesh without the need to\ninstall or manage the controller yourself.\n\nThe managed controller is designed to yield to the in-cluster controller.\nIf you are migrating from the in-cluster controller, you must delete the\nin-cluster controller from each cluster it is running on for the managed\ncontroller to take over. For more information, see\n[Disable the in-cluster Canonical Service controller](#disable-in-cluster-service-controller).\n\nTo enable the Managed controller: \n\nAnthos Features Page\n\n1. In the Google Cloud console, go to the **GKE Enterprise** Clusters page.\n\n [Go to the GKE Enterprise Clusters page](https://console.cloud.google.com/anthos/clusters)\n2. \"Register\" all the clusters in your mesh.\n\n3. In the Google Cloud console, go to the **GKE Enterprise** Features page.\n\n [Go to the GKE Enterprise Features page](https://console.cloud.google.com/anthos/features)\n4. Click **Enable** next to the \"Service Mesh\" feature\n\nAfter a few minutes, the Managed controller activates and creates Canonical\nServices for the workloads running on registered clusters in your mesh. Run\n`kubectl get canonicalservices --all-namespaces` to confirm that some\nCanonical Services have been created for the workloads in your mesh.\n\nGKE cluster creation\n\nIf you used the [**Enable Cloud Service Mesh** option when creating a new\nGKE cluster](/service-mesh/docs/managed/install-anthos-service-mesh-console), then the\nManaged Canonical Service Controller was installed by default.\n\nEnsure you are running the Managed Canonical Service Controller by running the\nfollowing command: \n\n```\ngcloud beta container hub mesh describe --project=PROJECT_ID\n```\n\nThe description states that the Canonical Services are reconciled successfully: \n\n projects/\u003cyour project number\u003e/locations/global/memberships/\u003cyour cluster 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\nIf the Canonical Services aren't reconciled successfully, there will either be\nan error message, or an output similar to the following message: \n\n projects/\u003cyour project number\u003e/locations/global/memberships/\u003cyour cluster 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.20/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\nManaged control plane installation\n\nIf you installed managed Cloud Service Mesh (with the\n[fleet API](/service-mesh/docs/managed/provision-managed-anthos-service-mesh) or with\n[`asmcli`](/service-mesh/docs/managed/provision-managed-anthos-service-mesh-asmcli)),\nthen the Managed Canonical Service Controller was installed by default.\n\nEnsure you are running the Managed Canonical Service Controller by running the\nfollowing command: \n\n```\ngcloud beta container hub mesh describe --project=PROJECT_ID\n```\n\nThe description states that the Canonical Services are reconciled successfully: \n\n projects/\u003cyour project number\u003e/locations/global/memberships/\u003cyour cluster 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\nIf the Canonical Services aren't reconciled successfully, there will either be\nan error message, or an output similar to the following message: \n\n projects/\u003cyour project number\u003e/locations/global/memberships/\u003cyour cluster 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.20/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\nWhat's next\n\nLearn about:\n\n- [Canonical Services](/service-mesh/v1.20/docs/canonical-service)\n- [Best practices in Canonical Services](/service-mesh/v1.20/docs/canonical-service-best-practices)\n- [Defining a Canonical Service](/service-mesh/v1.20/docs/observability/defining-canonical-service)\n- [Resolving Canonical Service issues](/service-mesh/v1.20/docs/troubleshooting/troubleshoot-canonical-service)"]]
