All clusters that have been
[added to your fleet](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/fleet-creation.md.txt)
appear in the Google Cloud console.

[Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)

The Google Cloud console offers a
central user interface for managing all your Kubernetes clusters and their
resources, no matter where they are running. All your resources are shown in a
single dashboard, which gives you visibility into your workloads across
multiple Kubernetes clusters. You can find out more about working with
Google Cloud clusters in the Google Cloud console in the
[GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/dashboards.md.txt).

For GKE clusters on Google Cloud, you see cluster details such
as nodes and workloads, provided that you have the relevant permissions.
The permissions are listed in the subsequent section,
[Required roles](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/console.md.txt#required_roles).

If your fleet includes clusters outside Google Cloud, you need to log in
to these clusters and view their details in the Google Cloud console. For
details, see the following section [Log in to clusters](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/console.md.txt#log-in).

## Required roles

If you are not a project owner, you must have the following Identity and Access Management roles at minimum to view clusters in the Google Cloud console:

- `roles/container.viewer`. This role lets users view the GKE
  Clusters page and other container resources in the Google Cloud console. For
  details about the permissions included in this role, or to grant a role with read/write permissions, see
  [Kubernetes Engine roles](https://docs.cloud.google.com/iam/docs/roles-permissions/container.md.txt)
  in the IAM documentation.

- `roles/gkehub.viewer`. This role lets users view clusters outside
  Google Cloud in the Google Cloud console. For details about the
  permissions included in this role, or to grant a role with read/write permissions, see
  [GKE Hub roles](https://docs.cloud.google.com/iam/docs/roles-permissions/gkehub.md.txt) in the
  IAM documentation.

- `roles/gkeonprem.viewer`. For Google Distributed Cloud users, this role is required in addition to `roles/gkehub.viewer` to view on-premises clusters on bare metal or VMware in the Google Cloud console. For details about the permissions included in this role, or to grant a role with read/write permissions, see [GKE on-prem roles](https://docs.cloud.google.com/iam/docs/roles-permissions/gkeonprem.md.txt) in the
  IAM documentation.

## View registered clusters

After you register a cluster to your project fleet, it appears in the
Google Cloud console in the
[GKE **Clusters** list](https://console.cloud.google.com/kubernetes/list).
However, to see more details such as nodes and workloads for any cluster outside
Google Cloud, you need to log in and authenticate to the cluster. Clusters
that require login show an orange warning triangle and prompt you to log in. The
following example shows the GKE **Clusters** page with two
clusters outside Google Cloud that require login.

![Screenshot of Google Kubernetes Engine clusters list](https://docs.cloud.google.com/static/anthos/images/cluster-login-prompt.png)

After you log in to the cluster, you can select the cluster
and view cluster details. These are the same details that you can see for a
GKE on Google Cloud cluster.

## Log in to clusters

If your fleet includes clusters outside Google Cloud, your
platform administrator needs to set up authentication so that you can log in to
these clusters and view their details in the Google Cloud console.

You need to know which authentication method your platform administrator has
set up so that you can log in to the Google Cloud console. Ask your platform
administrator which of the following authentication methods have been
configured:

- [Google identity](https://docs.cloud.google.com/kubernetes-engine/enterprise/multicluster-management/gateway/setup.md.txt)
- Third-party identity:
  - [GKE Identity Service with OIDC](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/per-cluster.md.txt)
  - [GKE Identity Service with Microsoft Entra ID (Azure AD)](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/per-cluster.md.txt#azure-ad-advanced)
  - [Third-party identity with the Connect gateway](https://docs.cloud.google.com/kubernetes-engine/enterprise/multicluster-management/gateway/setup-third-party.md.txt)
- [Bearer token](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/bearer-token-auth.md.txt)

Then, follow the instructions in the following sections to log in to your
clusters using the relevant authentication method.

### Log in using your Google Cloud identity

If your cluster is configured to use your
[Google Cloud identity](https://docs.cloud.google.com/kubernetes-engine/enterprise/multicluster-management/gateway/setup.md.txt),
follow these steps to log in:

1. Open the **GKE Clusters** page in the Google Cloud console.

   [Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)
2. Select the checkbox for the one or more clusters that you want to log in to.
   If you are selecting multiple clusters:

   - To select all of the clusters displayed on the page, select the checkbox
     in the table header row.

   - To select all of the clusters in the project that are not logged in,
     select the **Log in** option that accompanies the warning that
     you're not logged in to a certain number of clusters.

3. In the menu bar, click **Log in**.

4. Select **Use your Google identity to log in**.

5. Click **Log in**.

### Log in using OpenID Connect (OIDC)

Note that while GKE Identity Service also supports LDAP identity providers,
logging in using the Google Cloud console is supported for OIDC providers only.

If Microsoft Entra ID (Azure AD) is configured as an OIDC identity provider for your cluster using the `azuread` anchor in the ClientConfig, follow the instruction in [Log in using Microsoft Entra ID (Azure AD)](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/console.md.txt#log-in-azure-ad) instead.

If your cluster is configured to use an
[OIDC identity provider](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/per-cluster.md.txt) with GKE Identity Service, follow these steps
to log in:

1. Open the **GKE Clusters** page in the Google Cloud console.

   [Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)
2. Select the checkbox for the one or more clusters that you want to log in to.
   If you are selecting multiple clusters:

   - To select all of the clusters displayed on the page, select the checkbox
     in the table header row.

   - To select all of the clusters in the project that are not logged in,
     select the **Log in** option that accompanies the warning that
     you're not logged in to a certain number of clusters.

3. In the menu bar, click **Log in**.

4. Select **Authenticate with identity provider configured for the cluster**. You
   are redirected to your identity provider, where you might need to log in or
   consent to the Google Cloud console accessing your account.

5. Click **Log in**.

### Log in using Microsoft Entra ID (Azure AD)

If your cluster is configured to use
[Microsoft Entra ID (Azure ID)](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/per-cluster.md.txt) with GKE Identity Service [using the `azuread` anchor](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/per-cluster.md.txt#azure-ad-advanced) (also referred to as Azure AD advanced configuration), follow these steps
to log in:

1. Open the **GKE Clusters** page in the Google Cloud console.

   [Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)
2. Select the checkbox for the one or more clusters that you want to log in to.
   If you are selecting multiple clusters:

   - To select all of the clusters displayed on the page, select the checkbox
     in the table header row.

   - To select all of the clusters in the project that are not logged in,
     select the **Log in** option that accompanies the warning that
     you're not logged in to a certain number of clusters.

3. In the menu bar, click **Log in**.

4. Select **Authenticate with Microsoft Entra ID (formerly Azure AD)**. You
   are redirected to your identity provider, where you might need to log in or
   consent to the Google Cloud console accessing your account.

5. Click **Log in**.

### Log in using a third-party identity and the Connect gateway

If your cluster is configured to use [third-party identity with the Connect gateway](https://docs.cloud.google.com/kubernetes-engine/enterprise/multicluster-management/gateway/setup-third-party.md.txt), you can log in to the cluster with your third-party identity in the [Google Cloud workforce identity federation console](https://console.cloud.google), also known as the console (federated). Log in from the regular Google Cloud console is not supported.

Follow these steps to log in:

1. Go to the [Google Cloud workforce identity federation console](https://console.cloud.google), enter your provider ID, and sign in using your identity provider. Your platform administrator should provide you with all the details you need to sign in. To learn more about how this is set up, see [Set up user access to the console (federated)](https://docs.cloud.google.com/iam/docs/workforce-console-sso.md.txt).
2. Open the **GKE Clusters** page in the Google Cloud console.

   [Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)
3. Select the checkbox for the one or more clusters that you want to log in to.
   If you are selecting multiple clusters:

   - To select all of the clusters displayed on the page, select the checkbox
     in the table header row.

   - To select all of the clusters in the project that are not logged in,
     select the **Log in** option that accompanies the warning that
     you're not logged in to a certain number of clusters.

4. In the menu bar, click **Log in**.

5. Select **Use your third-party identity provider to log in**.

6. Click **Log in**.

### Log in using a bearer token

If your cluster is configured to use a
[Kubernetes service account's bearer token](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/setup/bearer-token-auth.md.txt),
follow these steps:

1. Open the **GKE Clusters** page in the Google Cloud console.

   [Go to GKE Clusters](https://console.cloud.google.com/kubernetes/list)
2. Select the checkbox for the one or more clusters that you want to log in to.
   If you are selecting multiple clusters:

   - To select all of the clusters displayed on the page, select the checkbox
     in the table header row.

   - To select all of the clusters in the project that are not logged in,
     select the **Log in** option that accompanies the warning that
     you're not logged in to a certain number of clusters.

3. In the menu bar, click **Log in**.

4. Select **Token** , and then fill in the **Token** field with the KSA's bearer
   token.

5. Click **Log in**.

## Auditing

Accesses via the Google Cloud console are [audit logged](https://kubernetes.io/docs/tasks/debug/debug-cluster/audit/) on the
cluster's API server.

## What's next

Learn more about:

- Working with clusters in the Google Cloud console in the [GKE documentation](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/dashboards.md.txt)
- Viewing cluster status and resource utilization in the Google Cloud console with the [GKE Enterprise overview](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/enterprise-overview-dashboard.md.txt)
- Setting up authentication to fleet clusters in [Secure your fleet](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/secure.md.txt#manage_identity)
- Connecting to fleet clusters from the command line:

  - [Setting up the Connect gateway](https://docs.cloud.google.com/kubernetes-engine/enterprise/multicluster-management/gateway.md.txt)
  - [Accessing clusters with GKE Identity Service](https://docs.cloud.google.com/kubernetes-engine/enterprise/identity/accessing.md.txt).
- [Managing fleet-level features](https://docs.cloud.google.com/kubernetes-engine/fleet-management/docs/manage-features.md.txt)