Gerenciar identidade com o serviço de identidade do GKE
Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Os clusters do Google Distributed Cloud são compatíveis com OpenID Connect (OIDC) e Protocolo leve de acesso a diretórios (LDAP) como
mecanismos de autenticação para interagir com o servidor da API Kubernetes de um cluster. usando o GKE Identity Service. O Serviço de identidade do GKE é um serviço de autenticação que permite levar suas soluções de identidade atuais para autenticação em vários ambientes do GKE Enterprise. Os usuários podem fazer login e usar os clusters do GKE pela linha de comando (todos os provedores) ou pelo Console do Google Cloud (somente OIDC), usando seu provedor de identidade atual.
É possível usar provedores de identidade locais e acessíveis publicamente com o GKE Identity Service. Por exemplo, se sua empresa executa um servidor de
Serviços de federação do Active Directory (ADFS, na sigla em inglês).
O servidor ADFS pode servir como seu provedor de OpenID. Você também pode usar serviços de provedor de identidade acessíveis publicamente, como o Okta. Os certificados de provedor de identidade
podem ser emitidos por uma autoridade de certificação pública
(CA, na sigla em inglês) conhecida ou por uma CA particular.
Se você já usa ou quer usar os IDs do Google para fazer login nos clusters do GKE em vez de um provedor OIDC ou LDAP, recomendamos o uso do gateway do Connect para autenticação. Saiba mais em Como se conectar a clusters registrados com o gateway do Connect.
Configure os clusters individualmente seguindo as instruções em
Como configurar clusters para o Serviço de identidade do GKE com o OIDC. Como a configuração no nível da frota é um recurso de visualização, use esta opção em ambientes de produção, se você estiver usando uma versão anterior do clusters do Google Distributed Cloud ou se precisar de recursos do GKE Identity Service que ainda não são compatíveis com Gerenciamento do ciclo de vida no nível da frota.
Após a configuração do GKE Identity Service, os usuários podem fazer login nos clusters configurados usando a linha de comando ou o Console do Google Cloud.
[[["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 2024-09-05 UTC."],[],[],null,["# Manage identity with GKE Identity Service\n\nGoogle Distributed Cloud supports [OpenID Connect (OIDC)](https://openid.net/connect/) and [Lightweight Directory Access Protocol (LDAP)](https://ldap.com/) as\nauthentication mechanisms for interacting with a cluster's Kubernetes API\nserver, using GKE Identity Service. GKE Identity Service is an authentication service that lets you bring your existing identity solutions for authentication to multiple GKE Enterprise environments. Users can log in to and use your GKE clusters from the command line (all providers) or from the Google Cloud console (OIDC only), all using your existing identity provider.\n\nYou can use both on-premises and publicly reachable identity providers with GKE Identity Service. For example, if your enterprise runs an\n[Active Directory Federation Services (ADFS)](https://docs.microsoft.com/en-us/windows-server/identity/active-directory-federation-services)\nserver, the ADFS server could serve as your OpenID provider. You might also use publicly-reachable identity provider services such as Okta. Identity provider certificates may be issued by either a well-known public certificate authority (CA), or by a private CA.\n| **Note:** The GKE Identity Service runs as a Pod inside the cluster control plane. During cluster lifecycle phases, the API Server is dynamically configured to use the in-cluster GKE Identity Service as the authentication webhook for all incoming requests. The API Server [isn't able to use in-cluster\n| DNS](https://github.com/kubernetes/minikube/issues/3772). As a result, the API Server is configured to access GKE Identity Service as a REST resource access. In audit logs, this invocation is recorded as a `CREATE` request to the Services or proxy resource by a `system:anonymous` user.\n\nFor an overview of how GKE Identity Service works, see [Introducing GKE Identity Service](/anthos/identity).\n\nIf you already use or want to use Google IDs to log in to your GKE clusters instead of an OIDC or LDAP provider, we recommend using the Connect gateway for authentication. Find out more in [Connecting to registered clusters with the Connect gateway](/anthos/multicluster-management/gateway).\n\nSetup process and options\n-------------------------\n\n### OIDC\n\n1. Register GKE Identity Service as a client with your OIDC provider following the instructions in [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 fleet level following the instructions in [Configuring clusters for fleet-level GKE Identity Service](/anthos/identity/setup/fleet-cluster) (preview, Google Distributed Cloud version 1.8 and higher). With this option, your authentication configuration is centrally managed by Google Cloud.\n - Configure your clusters individually following the instructions in [Configuring clusters for GKE Identity Service with OIDC](/anthos/identity/setup/per-cluster). Because fleet-level setup is a preview feature, you may want to use this option in production environments, if you are using an earlier version of Google Distributed Cloud, or if you require GKE Identity Service features that aren't yet supported with fleet-level lifecycle management.\n3. Set up user access to your clusters, including role-based access control (RBAC), following the instructions in [Setting up user access for GKE Identity Service](/anthos/identity/setup/user-access).\n\n### LDAP\n\n- Follow the instructions in [Set up GKE Identity Service with LDAP](/anthos/identity/setup/ldap).\n\nAccessing clusters\n------------------\n\nAfter GKE Identity Service has been set up, users can log in to configured clusters using either the command line or the Google Cloud console.\n\n- Learn how to log in to registered clusters with your OIDC or LDAP 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) (OIDC only).\n\nTroubleshoot the login flow\n---------------------------\n\nTo troubleshoot [login flows that authenticate directly on the\nGKE Identity Service server with a fully qualified domain name\n(FQDN)](/kubernetes-engine/enterprise/identity/setup/authenticate-fqdn-access),\nyou can use the GKE Identity Service diagnostic utility. The diagnostic\nutility simulates login flows with your OIDC provider to quickly identify\nconfiguration problems. This tool requires a version 1.32 or higher cluster and\nonly supports OIDC. For more information, see [GKE Identity Service\ndiagnostic\nutility](/kubernetes-engine/enterprise/identity/setup/anthos-v2-diagnostic-utility)."]]
