This page lists the permissions required by Google Distributed Cloud connected and the Identity and Access Management (IAM) roles that encapsulate them.
Distributed Cloud Edge Container API roles and permissions
The following table lists the Google Cloud project roles for the Distributed Cloud Edge Container API and the Distributed Cloud connected permissions that they encapsulate.
| Role | Permissions |
|---|---|
Edge Container Admin( Full access to Edge Container all resources. |
|
Edgecontainer Editor( Editor role for edgecontainer |
|
Edge Container Viewer( Read-only access to Edge Container all resources. |
|
Edge Container API Key Admin( Access to manage API Keys. |
|
Edge Container API Key Viewer( Read-only access to API Keys. |
|
Edge Container Identity Provider Admin( Access to manage Identity Providers. |
|
Edge Container Identity Provider Viewer( Read-only access to Identity Providers. |
|
Edge Container Machine User( Access to use Edge Container Machine resources. |
|
Edge Container Cluster offline Credential User( Access to get Edge Container cluster offline credentials |
|
Edge Container Service Account Admin( Access to manage Service Accounts. |
|
Edge Container Service Account Key Admin( Access to manage Service Account Keys. |
|
Edge Container Service Account Key Viewer( Access to view Service Account Keys. |
|
Edge Container Service Account Viewer( Read-only access to Service Accounts. |
|
Edge Container Zonal Project Admin( Access to manage zonal projects. |
|
Edge Container Zonal Project Viewer( Read-only access to zonal projects. |
|
Edge Container Zonal Service Admin( Access to mutate zonal service. |
|
Edge Container Zonal Service Viewer( Read-only access to zonal services. |
|
Edge Container Zone Iam Policy Admin( Access to manage Iam Policy in the zone. |
|
Edge Container Zone Iam Policy Viewer( Read-only access to Iam Policy in the zone. |
|
Edge Container Roles Viewer( Read-only access to Roles in the zone. |
|
Edge Container Zone Viewer( Read-only access to zones. |
|
Service agent roles
Service agent roles should only be granted to service agents.
| Role | Permissions |
|---|---|
Edge Container Cluster Service Agent( Grants the Edge Container Cluster Service Account access to manage resources. |
|
Edge Container Service Agent( Grants the Edge Container Service Account access to manage resources. |
|
Distributed Cloud Edge Network API roles and permissions
The following table lists the Google Cloud project roles for the Distributed Cloud Edge Network API and the Distributed Cloud connected permissions that they encapsulate.
| Role | Permissions |
|---|---|
Edge Network Admin( Full access to Edge Network all resources. |
|
Edge Network Editor( Editor role for Edge Network |
|
Edge Network Viewer( Read-only access to Edge Network all resources. |
|
GDC Hardware Management API roles and permissions
The following table lists the Google Cloud project roles for the GDC Hardware Management API and the Distributed Cloud connected permissions that they encapsulate.
| Role | Permissions |
|---|---|
GDC Hardware Management Admin Beta( Full access to GDC Hardware Management resources. |
|
Gdchardwaremanagement Viewer Beta( Viewer role for gdchardwaremanagement |
|
GDC Hardware Management Operator Beta( Create, read, and update access to GDC Hardware Management resources that support those operations. Also grants delete access to HardwareGroup resource. |
|
GDC Hardware Management Reader Beta( Readonly access to GDC Hardware Management resources. |
|
Connect gateway roles and permissions
The following list describes the Google Cloud project roles needed for connect gateway to access your clusters.
- Connect Gateway Admin (
roles/gkehub.gatewayAdmin): grants access to the connect gateway API. This role enables the use of thekubectlcommand-line tool for managing the cluster. - Connect Gateway Editor (
roles/gkehub.gatewayEditor): grants read and write access to the cluster. - Connect Gateway Reader (
roles/gkehub.gatewayReader): grants read-only access to the cluster. - GKE Hub Viewer (
roles/gkehub.viewer): grants the ability to retrieve kubeconfig files from the cluster.
Config Sync fleet packages roles and permissions
The following list describes the Google Cloud project roles required for creating and managing fleet packages.
- Config Delivery Admin (
roles/configdelivery.admin): required to create and manage fleet packages and rollouts. - Developer Connect Admin (
roles/developerconnect.admin): required to create and manage repository connections. - Project IAM Admin (
roles/resourcemanager.projectIamAdmin): required to grant necessary roles to the service account.
Fleet package service account roles
- Config Delivery Resource Bundle Publisher
(
roles/configdelivery.resourceBundlePublisher): allows the service account to create and manage resource bundles and releases. - Cloud Build Connection User (
roles/cloudbuild.connectionUser): allows the service account to use the Cloud Build repository connection. - Logging Log Writer (
roles/logging.logWriter): allows the service account to write build logs. - Artifact Registry Writer (
roles/artifactregistry.writer): allows the service account to push versioned package bundles to Artifact Registry. - Developer Connect Connection User
(
roles/developerconnect.connectionUser): allows the service account to use the Developer Connect connection.