The platform's user role management is implemented using Kubernetes RBAC (Role-Based Access Control). This system enables flexible permission configuration by associating roles with users.
A role represents a collection of permissions for operating Kubernetes resources on the platform. These permissions include:
Roles classify and combine permissions for different resources. By assigning roles to users and setting permission scopes, you can quickly grant resource operation permissions.
Permissions can be revoked just as easily by removing roles from users.
A role can have:
For example:
To meet common permission configuration scenarios, the platform provides the following default system roles. These roles enable flexible access control for platform resources and efficient permission management for users.
Role Name | Description | Role Level |
---|---|---|
Platform Administrator | Has full access to all business and resources on the platform | Platform |
Platform Auditors | Can view all platform resources and operation records, but has no other permissions | Platform |
Cluster Administrator (Alpha) | Manages and maintains cluster resources with full access to all cluster-level resources | Cluster |
Project Administrator | Manages namespace administrators and namespace quotas | Project |
namespace-admin-system | Manages namespace members and role assignments | Namespace |
Developers | Develops, deploys, and maintains custom applications within namespaces | Namespace |
The platform supports custom roles to enhance resource access control scenarios. Custom roles offer several advantages over system roles:
Exercise caution when updating or deleting custom roles. Deleting a custom role will automatically revoke all permissions granted by that role to bound users.