Permission Dependency of the CCE Console
Some CCE permissions policies depend on the policies of other cloud services. To view or use other cloud resources on the CCE console, you need to enable the system policy access control feature of IAM and assign dependency policies for the other cloud services.
- Dependency policies are assigned based on the CCE FullAccess or CCE ReadOnlyAccess policy you configure. For details, see Cluster Permissions (IAM-based).
- Only users and user groups with namespace permissions can gain the view access to resources in clusters of v1.11.7-r2 and later.
- If a user is granted the view access to all namespaces of a cluster, the user can view all namespaced resources (except secrets) in the cluster. To view secrets in the cluster, the user must gain the admin or edit role in all namespaces of the cluster.
- CustomedHPA and HPA policies take effect only after the cluster-admin permissions are configured for the namespace.
- The view role within a single namespace allows users to view resources only in the specified namespace.
Dependency Policy Configuration
To grant an IAM user the permissions to view or use resources of other cloud services on the CCE console, you must first grant the CCE Administrator, CCE FullAccess, or CCE ReadOnlyAccess policy to the user group to which the user belongs and then grant the dependency policies listed in Table 1 to the user. These dependency policies will allow the IAM user to access resources of other cloud services.
Enterprise projects can group and manage resources across different projects of an enterprise. Resources are thereby isolated. IAM allows you to implement fine-grained authorization. It is strongly recommended that you use IAM for permissions management.
If you use an enterprise project to set permissions for IAM users, the following restrictions apply:
- Storage resources are not available to enterprise projects. Therefore, when an enterprise project user queries the storage resources of clusters in an enterprise project other than Default on the CCE console, all buttons on the page are in gray and resources are not displayed.
- On the CCE console, enterprise projects cannot call the API used to obtain AOM monitoring data for cluster monitoring. Therefore, IAM users in these enterprise projects cannot query monitoring data.
- On the CCE console, enterprise projects cannot call the API to query the key pair created during node creation. Therefore, IAM users in these enterprise projects cannot use the key pair login mode. Only the password login mode is supported.
- After assigning the CCE FullAccess permission to an enterprise project, you need to configure the ecs:availabilityZones:list action on the IAM console so that the enterprise project users can create nodes. Otherwise, the system will prompt that they do not have the permission.
CCE supports fine-grained permissions configuration, but has the following restrictions:
- AOM does not support resource-level monitoring. After operation permissions on specific resources are configured using IAM's fine-grained cluster resource management function, IAM users can view cluster monitoring information on the Dashboard page of the CCE console, but cannot view the data on non-fine-grained metrics.
- After assigning the CCE FullAccess or CCE ReadOnlyAccess permissions on the IAM console, you need to configure the sfsturbo:*:* action to use SFS Turbo volumes. Otherwise, IAM users will fail to query SFS Turbo volumes in a cluster.
| Console Function | Dependent Services | Roles or Policies Required |
|---|---|---|
| Dashboard | Application Operations Management (AOM) |
|
| Workload management | Elastic Load Balance (ELB) Application Performance Management (APM) Application Operations Management (AOM) NAT Gateway Object Storage Service (OBS) Scalable File Service (SFS) | Except in the following cases, the user does not require any additional role to create workloads.
|
| Cluster management | Application Operations Management (AOM) Billing Center (BSS) |
|
| Node management | Elastic Cloud Server (ECS) | If the permission assigned to an IAM user is CCE Administrator, creating or deleting a node requires the ECS FullAccess or ECS Administrator policy and the VPC Administrator policy. |
| Network management | Elastic Load Balance (ELB) NAT Gateway | Except in the following cases, the user does not require any additional role to create a Service.
|
| Storage management | Object Storage Service (OBS) Scalable File Service (SFS) SFS Turbo |
The CCE Administrator role is required for importing storage devices. |
| Namespace management | / | / |
| Chart management | / | Huawei Cloud accounts and the IAM users with CCE Administrator assigned can use this function. |
| Add-on management | / | Huawei Cloud accounts and the IAM users with CCE Administrator, CCE FullAccess, or CCE ReadOnlyAccess assigned can use this function. |
| Permissions management | / |
|
| Configuration center | / |
|
| Help center | / | / |
| Switching to other related services | Software Repository for Container (SWR) Application Service Mesh (ASM) Application Operations Management (AOM) Multi-Cloud Container Platform (MCP) Cloud Eye (for viewing metrics of nodes and storage systems) | The CCE console provides links to other related services. To view or use these services, an IAM user must be assigned required permissions for the services. |
Last Article: Example: Designing and Configuring Permissions for Users in a Department
Next Article: Pod Security Policies
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.