Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Gerencie a identidade com o GKE Identity Service
O GKE no Azure oferece suporte ao OpenID Connect (OIDC) como um mecanismo de autenticação para interagir com o servidor da API do Kubernetes de um cluster, usando o Serviço de Identidade do GKE. O Serviço de Identidade do GKE é um serviço de autenticação que permite levar suas soluções de identidade existentes para autenticação a vários ambientes. Os usuários podem fazer login e usar seus clusters do GKE a partir da linha de comando ou doGoogle Cloud console, tudo usando seu provedor de identidade existente.
Se você já usa ou deseja usar identidades do Google para fazer login nos seus clusters do GKE, recomendamos usar o comando gcloud containers azure clusters get-credentials para autenticação. Saiba mais em Conectar e autenticar no seu cluster .
Para autenticar através do Google Cloud No console, você precisa registrar cada cluster que deseja configurar na frota do seu projeto. Para o GKE no Azure, isso é automático após a criação de um pool de nós.
Para permitir que os usuários se autentiquem por meio do Google Cloud No console, certifique-se de que todos os clusters que você deseja configurar estejam registrados na frota do seu projeto . Para o GKE no Azure, isso é automático após a criação de um pool de nós.
Depois que o GKE Identity Service for configurado em um cluster, os usuários poderão efetuar login nos clusters usando a linha de comando ou o Google Cloud console.
[[["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-06-12 UTC."],[],[],null,["# Manage identity with GKE Identity Service\n=========================================\n\nGKE on Azure supports\n[OpenID Connect (OIDC)](https://openid.net/connect/)\nas an\nauthentication mechanism for interacting with a cluster's Kubernetes API\nserver, using GKE Identity Service. GKE Identity Service is an\nauthentication service that lets you bring your existing identity solutions for\nauthentication to multiple environments. Users can log in to and\nuse your GKE clusters from the command line or from the\nGoogle Cloud console, all using your existing identity provider.\n\nFor an overview of how GKE Identity Service works, see\n[Introducing GKE Identity Service](/anthos/identity).\n\nIf you already use or want to use Google identities to log in to your\nGKE clusters, we recommend using the\n`gcloud containers azure clusters get-credentials` command for authentication. Find out\nmore in\n[Connect and authenticate to your cluster](/kubernetes-engine/multi-cloud/docs/azure/how-to/connect-and-authenticate-to-your-cluster#google-identity).\n\nOpenID Connect authentication\n-----------------------------\n\n### Before you begin\n\n1. To use OIDC authentication, users must be able to connect to the cluster's control\n plane. See\n [Connect to your cluster's control plane](/kubernetes-engine/multi-cloud/docs/azure/how-to/connect-and-authenticate-to-your-cluster#connect-to-vpn).\n\n2. To authenticate through the Google Cloud console, you must\n [register each cluster](/anthos/multicluster-management/connect/registering-a-cluster)\n that you want to configure with your project fleet. For GKE on Azure,\n this is automatic once you have created a node pool.\n\n3. To allow users to authenticate through the Google Cloud console, ensure that all\n clusters you want to configure are\n [registered with your project fleet](/anthos/multicluster-management/connect/registering-a-cluster).\n For GKE on Azure, this is automatic once you have created a node pool.\n\n### Setup process and options\n\n1. Register GKE Identity Service as a client with your OIDC provider\n following the instructions in\n [Configuring providers for GKE Identity Service](/anthos/identity/setup/provider).\n\n2. Choose from the following cluster configuration options:\n\n - Configure your clusters at the fleet-level following the instructions in\n [Configuring clusters for fleet-level GKE Identity Service](/anthos/identity/setup/fleet-cluster).\n With this option, your authentication configuration is centrally managed by\n Google Cloud.\n\n - Configure your clusters individually following the instructions in\n [Configuring clusters for GKE Identity Service with OIDC](/anthos/identity/setup/per-cluster).\n\n3. Set up user access to your clusters, including role-based access control\n (RBAC), following the instructions in\n [Setting up user access for GKE Identity Service](/anthos/identity/setup/user-access).\n\n### Accessing clusters\n\nAfter GKE Identity Service has been set up on a cluster, users can log in\nto clusters using either the command line or the Google Cloud console.\n\n- Learn how to log in to registered clusters with your OIDC ID in [Accessing clusters using GKE Identity Service](/anthos/identity/accessing).\n- Learn how to log in to clusters from the Google Cloud console in [Logging in to a cluster from the Google Cloud console](/anthos/multicluster-management/console/logging-in)."]]