Dashboard for Kubernetes (Beta)
all tiers

Introduced in GitLab 16.1, with flags named environment_settings_to_graphql, kas_user_access, kas_user_access_project, and expose_authorized_cluster_agents. This feature is in Beta.

Use the Dashboard for Kubernetes to understand the status of your clusters with an intuitive visual interface. The dashboard works with every connected Kubernetes cluster, whether you deployed them with CI/CD or GitOps.

For Flux users, the synchronization status of a given environment is not displayed in the dashboard. Issue 391581 proposes to add this functionality.

Configure a dashboard

Configure a dashboard to use it for a given environment. You can configure dashboard for an environment that already exists, or add one when you create an environment.

Prerequisite:

  • The agent for Kubernetes must be shared with the environment’s project, or its parent group, using the user_access keyword.

The environment already exists

  1. On the left sidebar, at the top, select Search GitLab () to find your project.
  2. Select Operate > Environments.
  3. Select the environment to be associated with the Kubernetes.
  4. Select Edit.
  5. Select a GitLab agent for Kubernetes.
  6. Select Save.

The environment doesn’t exist

  1. On the left sidebar, at the top, select Search GitLab () to find your project.
  2. Select Operate > Environments.
  3. Select New environment.
  4. Complete the Name field.
  5. Select a GitLab agent for Kubernetes.
  6. Select Save.

View a dashboard

To view a configured dashboard:

  1. On the left sidebar, at the top, select Search GitLab () to find your project.
  2. Select Operate > Environments.
  3. Expand the environment associated with GitLab agent for Kubernetes.
  4. Expand Kubernetes overview.

Troubleshooting

When working with the Dashboard for Kubernetes, you might encounter the following issues.

User cannot list resource in API group

You might get an error that states Error: services is forbidden: User "gitlab:user:<user-name>" cannot list resource "<resource-name>" in API group "" at the cluster scope.

This error happens when a user is not allowed to do the specified operation in the Kubernetes RBAC.

To resolve, check your RBAC configuration. If the RBAC is properly configured, contact your Kubernetes administrator.