Version 1.9. This is the most recent version. It's supported as outlined in the Anthos version support policy, offering the latest patches and updates for security vulnerabilities, exposures, and issues impacting Anthos clusters on bare metal. For release details, see the release notes 1.9. For a complete list of each minor and patch release in chronological order, see the combined release notes.

Available supported versions: 1.9  |   1.8  |   1.7  |  

Manage identity with Anthos Identity Service

Anthos clusters on bare metal supports OpenID Connect (OIDC) and Lightweight Directory Access Protocol (LDAP) as authentication mechanisms for interacting with a cluster's Kubernetes API server, using Anthos Identity Service. Anthos Identity Service is an authentication service that lets you bring your existing identity solutions for authentication to multiple Anthos environments. Users can log in to and use your Anthos clusters from the command line (all providers) or from the Cloud Console (OIDC only), all using your existing identity provider.

Anthos Identity Service works with any kind of bare metal cluster: admin, user, hybrid, or standalone. You can use both on-premises and publicly reachable identity providers. For example, if your enterprise runs an Active Directory Federation Services (ADFS) server, 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.

For an overview of how Anthos Identity Service works, see Introducing Anthos Identity Service.

If you already use or want to use Google IDs to log in to your Anthos 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.

Before you begin

  • Note that headless systems are unsupported. A browser-based authentication flow is used to prompt users for consent and authorize their user account.

  • To authenticate through the Google Cloud Console, each cluster that you want to configure must be registered with your project fleet.

Setup process and options

OIDC

  1. Register Anthos Identity Service as a client with your OIDC provider following the instructions in Configuring providers for Anthos Identity Service.

  2. Choose from the following cluster configuration options:

    • Configure your clusters at fleet level following the instructions in Configuring clusters for fleet-level Anthos Identity Service (preview, Anthos clusters on bare metal version 1.8 and higher). With this option, your authentication configuration is centrally managed by Google Cloud.
    • Configure your clusters individually following the instructions in Configuring clusters for Anthos Identity Service with OIDC. 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 Anthos clusters on bare metal, or if you require Anthos Identity Service features that aren't yet supported with fleet-level lifecycle management.
  3. Set up user access to your clusters, including role-based access control (RBAC), following the instructions in Setting up user access for Anthos Identity Service.

LDAP

Access clusters

After Anthos Identity Service has been set up, users can log in to configured clusters using either the command line or the Cloud Console.