Create Workspace, Project, Account and Role

KubeSphere needs to be installed in your machine.

About 15 minutes.

The multi-tenant system of KubeSphere features three levels of hierarchical structure which are cluster, workspace and project. A project in KubeSphere is a Kubernetes namespace.

You can create multiple workspaces within a Kubernetes cluster. Under each workspace, you can also create multiple projects.

Each level has multiple built-in roles. Besides, KubeSphere allows you to create roles with customized authorization as well. The KubeSphere hierarchy is applicable for enterprise users with different teams or groups, and different roles within each team.

After KubeSphere is installed, you need to add different users with varied roles to the platform so that they can work at different levels on various resources. Initially, you only have one default account, which is admin, granted the role . In the first task, you will create an account user-manager and further create more accounts as user-manager.

1. Log in the web console as admin with the default account and password (admin/[[email protected]](https://kubesphere.io/cdn-cgi/l/email-protection)).

Tip

For account security, it is highly recommended that you change your password the first time you log in the console. To change your password, select User Settings in the drop-down menu in the top-right corner. In Password Setting, set a new password.

In Account Roles, there are four available built-in roles as shown below. The account to be created next will be assigned the role users-manager.

Note

Built-in roles are created automatically by KubeSphere and cannot be edited or deleted.

1. In Accounts, click Create. In the pop-up window, provide all the necessary information (marked with *) and select users-manager for Role. Refer to the image below as an example.

Click OK after you finish. A newly-created account will display in the account list in Accounts.

1. Log out of the console and log back in with the account user-manager to create four accounts that will be used in the following tutorials.

Tip

To log out, click your username in the top-right corner and select Log Out.

For detailed information about the four accounts you need to create, refer to the table below.

1. Verify the four accounts created.

In this task, you need to create a workspace using the account ws-manager created in the previous task. As the basic logic unit for the management of projects, DevOps projects and organization members, workspaces underpin multi-tenant system of KubeSphere.

1. Log in KubeSphere as ws-manager which has the authorization to manage all workspaces on the platform. Click Platform in the top-left corner. In Workspaces, you can see there is only one default workspace system-workspace listed, where system-related components and services run. You are not allowed to delete this workspace.

1. Click Create on the right, name the new workspace demo-workspace and set the user ws-admin as the workspace manager shown in the screenshot below:

Click Create after you finish.

1. Log out of the console and log back in as ws-admin. In Workspace Settings, select Workspace Members and click Invite Member.

1. Invite both and project-regular to the workspace. Grant them the role workspace-self-provisioner and workspace-viewer respectively.

Note

The actual role name follows a naming convention: workspace name-role name. For example, in this workspace named demo, the actual role name of the role workspace-viewer is demo-workspace-viewer.

1. After you add both project-admin and project-regular to the workspace, click OK. In Workspace Members, you can see three members listed.

In this task, you need to create a project using the account project-admin created in the previous task. A project in KubeSphere is the same as a namespace in Kubernetes, which provides virtual isolation for resources. For more information, see Namespaces.

1. Log in KubeSphere as project-admin. In Projects, click Create.

1. Enter the project name (e.g. demo-project) and click OK to finish. You can also add an alias and description for the project.

1. In Projects, click the project created just now to view its detailed information.

1. In the overview page of the project, the project quota remains unset by default. You can click Set and specify resource requests and limits based on your needs (e.g. 1 core for CPU and 1000Gi for memory).

Info

The user granted the role operator will be a project maintainer who can manage resources other than users and roles in the project.

Set Gateway

Before creating a route, you need to enable a gateway for this project. The gateway is an NGINX Ingress controller running in the project.

Info

A route refers to Ingress in Kubernetes, which is an API object that manages external access to the services in a cluster, typically HTTP.

1. To set a gateway, go to Advanced Settings in Project Settings and click Set Gateway. The account project-admin is still used in this step.

1. Choose the access method NodePort and click Save.

1. Under Internet Access, it can be seen that the Gateway Address and the NodePort of http and https all display in the page.

If you want to expose services using the type LoadBalancer, you need to use the LoadBalancer plugin of cloud providers. If your Kubernetes cluster is running in a bare metal environment, it is recommended you use as the LoadBalancer plugin.

After you finish the above tasks, you know that users can be granted different roles at different levels. The roles used in previous tasks are all built-in ones created by KubeSphere itself. In this task, you will learn how to define a role yourself to meet the needs in your work.

1. Log in the console as admin again and go to Access Control.
2. In Account Roles, there are four system roles listed which cannot be deleted or edited. Click Create and set a Role Identifier. In this example, a role named roles-manager will be created.

Note

It is recommended you enter a description for the role as it explains what the role is used for. The role created here will be responsible for role management only, including adding and deleting roles.

Click Edit Authorization to continue.

1. In Access Control, select the authorization that you want the user granted this role to have. For example, Users View, Roles Management and Roles View are selected for this role. Click OK to finish.

Note

Depend on means the major authorization (the one listed after Depend on) needs to be selected first so that the affiliated authorization can be assigned.

1. Newly-created roles will be listed in Account Roles. You can click the three dots on the right to edit it.

1. In Accounts, you can add a new account and grant it the role roles-manager or change the role of an existing account to roles-manager by editing it.

Note

The role of roles-manager overlaps with users-manager while the latter is also capable of user management. This example is only for demonstration purpose. You can create customized roles based on your needs.

Note

To create a DevOps project, you need to install KubeSphere DevOps system in advance, which is a pluggable component providing CI/CD pipelines, Binary-to-image, Source-to-image features, and more. For more information about how to enable DevOps, see KubeSphere DevOps System.

1. Log in the console as project-admin for this task. In DevOps Projects, click Create.

1. Enter the DevOps project name (e.g. demo-devops) and click OK. You can also add an alias and description for the project.

1. In DevOps Projects, click the project created just now to view its detailed information.

1. Go to Project Management and select Project Members. Click Invite Member to grant project-regular the role of operator, who is allowed to create pipelines and credentials.