1. Release Notes
    1. Release Notes - 2.0.2Latest
    1. Release Notes - 2.0.1
    1. Release Notes - 2.0.0
  1. Introduction
    1. Introduction
    1. Features
    1. Architecture
    1. Advantages
    1. Glossary
  1. Installation
    1. Intruction
      1. Intro
      2. Port Requirements
    1. Install on Linux
      1. All-in-One Installation
      2. Multi-Node Installation
      3. Installing HA Master and Etcd Cluster
      4. Storage Configuration Instruction
    1. Install on Kubernetes
      1. Prerequisites
      2. Online Installation
      3. Offline Installation
    1. Related Tools
      1. Integrating Harbor Registry
    1. Cluster Operation
      1. Adding New Nodes
      2. High Risk Operation
      3. Uninstalling KubeSphere
  1. Quick Start
    1. Getting Started with Multitenancy
    1. Exposing your APP using Ingress
    1. Deploying a MySQL Application
    1. Deploying a Wordpress Website
    1. Job to compute π to 2000 places
    1. Deploying Grafana using APP Template
    1. Creating Horizontal Pod Autoscaler
    1. S2i: Publish your app without Dockerfile
    1. Canary Release of Microservice APP
    1. CI/CD based on Spring Boot Project
    1. Building a Pipeline in a Graphical Panel
    1. CI/CD based on GitLab and Harbor
    1. Ingress-Nginx for Grayscale Release
  1. Cluster Admin Guide
    1. Multi-tenant Management
      1. Overview of Multi-tenant Management
      2. Overview of Role Management
    1. Platform Management
      1. Account Management
      2. Platform Roles Management
    1. Infrastructure
      1. Service Components
      2. Nodes
      3. Storage Classes
    1. Monitoring Center
      1. Physical Resources
      2. Application Resources
    1. Application Repository
    1. Jenkins System Settings
  1. User Guide
    1. Application Template
    1. Workloads
      1. Deployments
      2. StatefulSets
      3. DaemonSets
      4. Jobs
      5. CronJobs
    1. Storage
      1. Volumes
    1. Network & Services
      1. Services
      2. Routes
    1. Configuration Center
      1. Secret
      2. ConfigMap
      3. Image Registry
    1. Project Settings
      1. Basic Information
      2. Member Roles
      3. Project Members
      4. Internet Access
    1. DevOps Project
      1. DevOps Project Management
      2. DevOps Project Management
      3. DevOps Project Management
      4. DevOps Project Management
      5. DevOps Project Management
  1. Development Guide
    1. Preparing the Development Environment
    1. Development Workflow
  1. API Documentation
    1. API Guide
    1. How to invoke KubeSphere API
KubeSphere®️ 2020 All Rights Reserved.

Overview of Role Management

In enterprise bussiness scenarios, the resource hierarchy of KubeSphere is divided into three levels:

  • Cluster
  • Workspace
  • Project / DevOps Project

Multi-level division is also the basis to realize multi-tenant and resource isolation. For the user to create an account, the first by the cluster admin or workspace by invite new members to join the workspace, and then can be under the same corporate space project or enterprise project admin, invited to join the project and enterprise engineering, invited the admin can give the corresponding role for new members, and different roles with different operating rights, the role of the platform built in several commonly used for use. At the same time, the platform supports the admin to customize the role and permission list. The following describes the authority management and built-in roles at different levels.

Role Permission Management

Roles are divided into three levels: cluster, workspace, and project/DevOps projects, which relate users to different levels of resources.


Built-in Role Permissions

The reason why multiple built-in roles are divided in cluster and cluster space is to conduct fine-grained management according to the permissions of different roles, so that members with different roles can more accurately view and manage resources in cluster or workspace. Only after the permissions of different roles are subdivided can the control and isolation of different resources in multi-tenant mode be more secure. The following figure summarizes which permissions different roles have in the cluster and workspace.

Overview of Built-in Role Permissions


Cluster Roles

Cluster includes user management, workspace management and resource management at the level of various clusters. Cluster level authority, mainly for nodes, cluster monitoring, storage type, workspace and other cluster level resource control.

Built-in cluster role:

Built-in Roles Description
cluster-admin Cluster admin can manage all the resources in the cluster.
workspaces-manager Manage all the workspaces in the cluster and the projects and engineering resources below.
cluster-regular Regular users, they do not have any resource operation rights before they are invited to join the workspace.

Workspace roles:

Individual tenants, projects, and Devops projects are all in the workspace, which also has members that can be added from the cluster's user pool. When an workspace is created, the creator defaults to the admin role under that space. The admin of the workspace can create project, DevOps engineering resources in the workspace and invite users to join the workspace from the user pool of the cluster.

Built-in workspace role:

Built-in Roles Description
workspace-admin Workspace manager, can manage all resources under the workspace.
workspace-regular Workspace regular member to create projects and projects in the workspace.
workspace-viewer Observer of the workspace to view all resource information in the workspace.

Project Roles

Cluster computing resource virtual partition, the project has a resource quota limit. When a project, DevOps project is created, the creator defaults to the admin role under the project or DevOps project. Users can be searched and added from the user pool under the workspace by the project admin, who invites members within the project.

Built-in project role:

Built-in Roles Description
admin project manager, can manage all the resources under the project.
operator project maintainer manages resources under the project in addition to users and roles.
viewer project viewer that can view all the resources under a project.

Overview of built-in role permissions

Resource/Permission/Role admin operator viewer
Projects management view/edit/delete view view
Members management view/create/edit/delete / /
Roles management view/create/edit/delete / /
Deployments view/create/edit/delete/scale view/create/edit/delete/scale view
Statefulsets view/create/edit/delete/scale view/create/edit/delete/scale view
Daemonsets view/create/edit/delete view/create/edit/delete view
Pods management remote connection remote connection remote connection
Service manages view/create/edit/delete view/create/edit/delete view
External Access management view/create/edit/delete view/create/edit/delete view
Routers management to view/create/edit/delete view/create/edit/delete view
Volume view/create/edit/delete view/create/edit/delete view
Applications management view/deploy/delete view/deploy/delete view
Jobs management view/create/edit/delete view/create/edit/delete view
CronJobs management view/create/edit/delete view/create/edit/delete view
Secrets management view/create/edit/delete view/create/edit/delete view
CofigMaps management view/create/edit/delete view/create/edit/delete view

The Role of DevOps

Facilitate fine-grained management of DevOps projects. The admin of the DevOps project search and add users from the user pool under the workspace.

Built-in DevOps engineering roles:

Built-in Roles Description
owner the owner of the project, can do all the actions of the project.
Maintainer can maintain credentials and pipeline configuration within the project.
Developer can trigger and view pipeline.
Reporter can check pipeline status.