Google Distributed Cloud は、GKE Identity Service を使用してクラスタの Kubernetes API サーバーとやり取りする認証メカニズムとして、OpenID Connect（OIDC）と Lightweight Directory Access Protocol（LDAP）をサポートしています。GKE Identity Service は、認証を目的とする既存の ID ソリューションを複数の GKE Enterprise 環境で利用できるようにする認証サービスです。ユーザーは、既存の ID プロバイダを使用してコマンドライン（すべてのプロバイダ）またはGoogle Cloud コンソール（OIDC のみ）からログインし、GKE クラスタを使用できます。
GKE Identity Service は、管理、ユーザー、ハイブリッド、スタンドアロンなど、あらゆる種類のベアメタル クラスタで動作します。オンプレミスと公開アクセス可能な ID プロバイダの両方を使用できます。たとえば、企業で Active Directory フェデレーション サービス（ADFS）サーバーが実行されている場合、ADFS サーバーは OpenID プロバイダとして機能します。Okta など、一般公開されている ID プロバイダ サービスを使用することもできます。ID プロバイダの証明書は有名なパブリック認証局（CA）またはプライベート CA によって発行されます。
OIDC による GKE Identity Service 用のクラスタを構成するの手順に沿って、クラスタを個別に構成します。フリートレベルの設定はプレビュー機能です。以前のバージョンの Google Distributed Cloud を使用している場合、またはフリートレベルのライフサイクル管理でサポートされていない GKE Identity Service 機能が必要な場合は、本番環境ではこのオプションを使用できます。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["わかりにくい","hardToUnderstand","thumb-down"],["情報またはサンプルコードが不正確","incorrectInformationOrSampleCode","thumb-down"],["必要な情報 / サンプルがない","missingTheInformationSamplesINeed","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2025-09-01 UTC。"],[],[],null,["Google Distributed Cloud supports [OpenID Connect\n(OIDC)](https://openid.net/connect/) and [Lightweight Directory\nAccess Protocol (LDAP)](https://ldap.com/) as authentication\nmechanisms for interacting with a cluster's Kubernetes API server, using\nGKE Identity Service. GKE Identity Service is an authentication service\nthat lets you bring your existing identity solutions for authentication to\nyour clusters. Users can log in to and use clusters from the command line\n(all providers) or from the Google Cloud console (OIDC only), all using your\nexisting identity provider.\n\nGKE Identity Service works with any kind of bare metal cluster: admin, user,\nhybrid, or standalone. You can use both on-premises and publicly reachable\nidentity providers. For example, if your enterprise runs an [Active Directory\nFederation Services\n(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\npublicly-reachable identity provider services such as Okta. Identity provider\ncertificates may be issued by either a well-known public certificate authority\n(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\nGKE Identity Service](/kubernetes-engine/enterprise/identity).\n\nIf you already use or want to use Google IDs to sign in to your GKE clusters\ninstead of an OIDC or LDAP provider, we recommend using connect gateway\nfor authentication. Find out more in [Connecting to registered clusters with the\nconnect gateway](/kubernetes-engine/enterprise/multicluster-management/gateway).\n\nBefore you begin\n\n- To prompt users for consent and authorize their user account, a\n browser-based authentication flow is used. Headless systems aren't\n supported.\n\n- To authenticate through the Google Cloud console, each cluster that you want to\n configure must be [registered with your project\n fleet](/kubernetes-engine/fleet-management/docs/fleet-creation).\n\nSetup process and options\n\nGKE Identity Service supports identity providers using the following\nprotocols:\n\n- [OpenID Connect (OIDC)](https://openid.net/connect/). We provide\n specific instructions for setup for some popular OpenID providers, including\n Microsoft, but you can use any provider that implements OIDC.\n\n- [Lightweight Directory Access Protocol\n (LDAP)](https://ldap.com/). You can use\n GKE Identity Service to authenticate using LDAP with Active Directory\n or an LDAP server.\n\nOIDC\n\n1. Register GKE Identity Service as a client with your OIDC provider\n following the instructions in [Configuring providers for\n GKE Identity Service](/kubernetes-engine/enterprise/identity/setup/provider).\n\n2. Choose from the following cluster configuration options:\n\n - Configure your clusters at fleet level following the instructions in\n [Configuring clusters for fleet-level\n GKE Identity Service](/kubernetes-engine/enterprise/identity/setup/fleet-cluster) (preview,\n Google Distributed Cloud version 1.8 and higher). With this option, your\n authentication configuration is centrally managed by Google Cloud.\n\n - Configure your clusters individually following the instructions in\n [Configuring clusters for GKE Identity Service with\n OIDC](/kubernetes-engine/enterprise/identity/setup/per-cluster). Because fleet-level setup is\n a preview feature, you may want to use this option in production\n environments, if you are using an earlier version of\n Google Distributed Cloud, or if you require GKE Identity Service\n features that aren't yet supported with fleet-level lifecycle\n management.\n\n3. Set up user access to your clusters, including role-based access control\n (RBAC), following the instructions in [Setting up user access for\n GKE Identity Service](/kubernetes-engine/enterprise/identity/setup/user-access).\n\nLDAP\n\nTo get started with LDAP, follow the instructions in [Set up\nGKE Identity Service with\nLDAP](/kubernetes-engine/enterprise/identity/setup/ldap).\n\nAccess clusters\n\nAfter GKE Identity Service has been set up, users can sign in to configured\nclusters using either the command line or the Google Cloud console.\n\n- Learn how to sign in to registered clusters with your OIDC or LDAP ID in\n [Accessing clusters using\n GKE Identity Service](/kubernetes-engine/enterprise/identity/accessing).\n\n- Learn how to sign in to clusters from the Google Cloud console in [Work\n with clusters from the\n Google Cloud console](/kubernetes-engine/fleet-management/docs/console)\n (OIDC only).\n\nTroubleshoot the login flow\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)."]]
