Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Como ativar e desativar o controlador de serviço canônico
Observação:os serviços canônicos são compatíveis com
a versão 1.6.8 do Cloud Service Mesh e versões mais recentes.
O controlador de serviços canônicos agrupa as cargas de trabalho que pertencem ao mesmo serviço lógico
e é necessário para a funcionalidade completa do painel de serviços
no Google Cloud console.
Todas as instalações gerenciadas do Cloud Service Mesh e instalações no cluster
com o asmcli da versão 1.25 provisionadas com o controlador de serviço canônico
gerenciado. O controlador de serviço canônico no cluster foi descontinuado e
não vai receber mais atualizações. Embora as implantações atuais do controlador
no cluster continuem funcionando, recomendamos migrar para o
controlador de serviço canônico gerenciado para garantir a compatibilidade com versões
futuras, acesso aos recursos mais recentes e suporte contínuo.
Para determinar se o controlador de serviço canônico no cluster está ativado no
cluster:
kubectlgetservices-nasm-system
Desativar o controlador de serviço canônico no cluster
Para implantações de controladores no cluster, migre para o controlador de serviço canônico gerenciado. Siga o
guia de migração.
Ativar o controlador de serviço canônico gerenciado
Se você instalou o Cloud Service Mesh gerenciado, o Controlador de serviço canônico gerenciado foi instalado por padrão. Além disso, todas as instalações do Cloud Service Mesh
no cluster com o asmcli a partir da versão 1.25 serão
provisionadas com o controlador de serviço canônico gerenciado.
Verifique se você está executando o controlador de serviço canônico gerenciado executando
o seguinte comando:
Substitua FLEET_PROJECT_ID pelo ID do seu projeto host da frota. Geralmente,
o FLEET_PROJECT_ID tem o mesmo nome do projeto.
Se a descrição indicar que os serviços canônicos foram reconciliados
com sucesso, o controlador de serviço canônico gerenciado estará funcionando como
esperado. Você não precisa fazer mais nada.
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'
Se a descrição indicar que o controlador de serviço canônico gerenciado está
retornando ao controlador no cluster, siga o guia de migração.
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
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 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/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)"]]
