本页面列出了 Google Distributed Cloud 联网配置 所需的权限,以及封装这些权限的 Identity and Access Management (IAM) 角色。
Distributed Cloud Edge Container API 角色和权限
下表列出了 Distributed Cloud Edge Container API 的 Google Cloud 项目角色以及它们封装的 Distributed Cloud 连接权限。
| 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 角色和权限
下表列出了 Distributed Cloud Edge Network API 的 Google Cloud 项目角色以及它们封装的 Distributed Cloud Connected 权限。
| 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 角色和权限
下表列出了 GDC 硬件管理 API 的 Google Cloud 项目角色以及它们封装的分布式云连接权限。
| 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 网关角色和权限
以下列表介绍了连接网关访问集群所需的 Google Cloud 项目角色。
- Connect Gateway Admin (
roles/gkehub.gatewayAdmin):授予对 Connect Gateway API 的访问权限。此角色支持使用kubectl命令行工具管理集群。 - Connect Gateway Editor (
roles/gkehub.gatewayEditor):授予对集群的读写权限。 - Connect Gateway Reader (
roles/gkehub.gatewayReader):授予对集群的只读访问权限。 - GKE Hub Viewer (
roles/gkehub.viewer):授予从集群检索 kubeconfig 文件的权限。
Config Sync 舰队软件包角色和权限
下表列出了创建和管理 Fleet 软件包所需的 Google Cloud 项目角色。
- Config Delivery Admin (
roles/configdelivery.admin):创建和管理舰队软件包及发布所需的角色。 - Developer Connect Admin (
roles/developerconnect.admin):创建和管理代码库连接时需要此角色。 - Project IAM Admin (
roles/resourcemanager.projectIamAdmin):需要此角色才能向服务账号授予必要的角色。
舰队软件包服务账号角色
- Config Delivery Resource Bundle Publisher (
roles/configdelivery.resourceBundlePublisher):允许服务账号创建和管理资源包及发布版本。 - Cloud Build 连接用户 (
roles/cloudbuild.connectionUser):允许服务账号使用 Cloud Build 代码库连接。 - Logging Log Writer (
roles/logging.logWriter):允许服务账号写入 build 日志。 - Artifact Registry Writer (
roles/artifactregistry.writer):允许服务账号将版本化的软件包捆绑包推送到 Artifact Registry。 - Developer Connect Connection User (
roles/developerconnect.connectionUser):允许服务账号使用 Developer Connect 连接。
VM Runtime on GDC 的集群内 RBAC 角色
VM Runtime on GDC 使用基于角色的访问权限控制 (RBAC) 来设置和强制执行集群内代管式资源的权限。权限从 Identity and Access Management 映射到本地 Kubernetes RBAC,并通过舰队成员资格进行管理。
VM Runtime on GDC 提供四种预配置的 ClusterRole。以下列表介绍了这些角色。
kubevm.admin:授予对所有虚拟机相关资源的完整访问权限。kubevm.edit:授予对所有与虚拟机相关的资源的读取和写入权限。kubevm.view:授予对所有与虚拟机相关的资源的读取权限。kubevm.cluster.view:授予对集群级资源的读取权限。
这些角色会聚合到以下 Kubernetes 默认角色:
kubevm.admin映射到adminkubevm.edit映射到editkubevm.view映射到view
具有默认 edit 角色的用户会自动获得 kubevm.edit 权限。