Supported Actions in RBAC

Supported Actions

CCI provides system-defined policies that can be directly used in IAM. You can also create custom policies and use them to supplement system-defined policies, implementing more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

• Permissions: statements that allow or deny certain operations in a policy
• APIs: REST APIs that can be called by a user who has been granted specific permissions
• Actions: specific operations that are allowed or denied
• Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
• IAM projects or enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management.

CCI supports the following actions in custom policies:

• Lifecycle management actions, such as the actions supported by the APIs for querying CCI namespace list, querying the CCI pod list, querying a CCI pod, creating a CCI pod, and querying CCI pod logs
• ConfigMap or secret management actions, such as the actions supported by the APIs for creating, deleting, and modifying a ConfigMap, and for creating and deleting a secret

Lifecycle Management Actions