mirror of
https://github.com/kubesphere/website.git
synced 2025-12-28 14:43:02 +00:00
Update Docs: create workspace and roles-3.1.1
Signed-off-by: adakisme <serenashe@yunify.com>
This commit is contained in:
adakisme
parent
0fbb150bac
commit
7634bea94d
|
|
@ -76,12 +76,33 @@ After KubeSphere is installed, you need to add different users with varied roles
|
|||
To log out, click your username in the upper-right corner and select **Log Out**.
|
||||
{{</ notice >}}
|
||||
|
||||
| Account | Role | Description |
|
||||
| ----------------- | -------------------- | ------------------------------------------------------------ |
|
||||
| `ws-manager` | `workspaces-manager` | Create and manage all workspaces. |
|
||||
| `ws-admin` | `platform-regular` | Manage all resources in a specified workspace (This account is used to invite new members to a workspace in this example). |
|
||||
| `project-admin` | `platform-regular` | Create and manage projects and DevOps projects, and invite new members into the projects. |
|
||||
| `project-regular` | `platform-regular` | `project-regular` will be invited to a project or DevOps project by `project-admin`. This account will be used to create workloads, pipelines and other resources in a specified project. |
|
||||
<table>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th width='140'>Account</th>
|
||||
<th width='160'>Role</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-manager</code></td>
|
||||
<td><code>workspaces-manager</code></td>
|
||||
<td>Create and manage all workspaces.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-admin</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td>Manage all resources in a specified workspace (This account is used to invite new members to a workspace in this example).</td>
|
||||
</tr><tr>
|
||||
<td><code>project-admin</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td>Create and manage projects and DevOps projects, and invite new members into the projects.</td>
|
||||
</tr><tr>
|
||||
<td><code>project-regular</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td><code>project-regular</code> will be invited to a project or DevOps project by <code>project-admin</code>. This account will be used to create workloads, pipelines and other resources in a specified project.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
5. Verify the four accounts created.
|
||||
|
||||
|
|
@ -91,15 +112,9 @@ After KubeSphere is installed, you need to add different users with varied roles
|
|||
|
||||
In this step, you create a workspace using the account `ws-manager` created in the previous step. As the basic logic unit for the management of projects, DevOps projects and organization members, workspaces underpin the multi-tenant system of KubeSphere.
|
||||
|
||||
1. Log in to KubeSphere as `ws-manager` which has the permission to manage all workspaces on the platform. Click **Platform** in the top-left corner and select **Access Control**. 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. Log in to KubeSphere as `ws-manager` which has the permission to manage all workspaces on the platform. Click **Platform** in the upper-left corner and select **Access Control**. In **Workspaces**, you can see there is only one default workspace `system-workspace`, where system-related components and services run. You are not allowed to delete this workspace.
|
||||
|
||||
|
||||
|
||||
2. 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.
|
||||
2. Click **Create** on the right, set a name for the new workspace (for example, `demo-workspace`) and set the user `ws-admin` as the workspace manager. Click **Create** after you finish.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -109,77 +124,81 @@ In this step, you create a workspace using the account `ws-manager` created in t
|
|||
|
||||
3. Log out of the console and log back in as `ws-admin`. In **Workspace Settings**, select **Workspace Members** and click **Invite Member**.
|
||||
|
||||
|
||||
|
||||
4. Invite both `project-admin` and `project-regular` to the workspace. Grant them the role `workspace-self-provisioner` and `workspace-viewer` respectively.
|
||||
4. Invite both `project-admin` and `project-regular` to the workspace. Assign them the role `workspace-self-provisioner` and `workspace-viewer` respectively and click **OK**.
|
||||
|
||||
{{< notice note >}}
|
||||
The actual role name follows a naming convention: `<workspace name>-<role name>`. For example, in this workspace named `demo-workspace`, the actual role name of the role `viewer` is `demo-workspace-viewer`.
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
5. After you add both `project-admin` and `project-regular` to the workspace, click **OK**. In **Workspace Members**, you can see three members listed.
|
||||
5. In **Workspace Members**, you can see three members listed.
|
||||
|
||||
| Account | Role | Description |
|
||||
| ----------------- | ---------------------------- | ------------------------------------------------------------ |
|
||||
| `ws-admin` | `workspace-admin` | Manage all resources under the workspace (Use this account to invite new members to the workspace). |
|
||||
| `project-admin` | `workspace-self-provisioner` | Create and manage projects and DevOps projects, and invite new members to join the projects. |
|
||||
| `project-regular` | `workspace-viewer` | `project-regular` will be invited by `project-admin` to join a project or DevOps project. The account can be used to create workloads, pipelines, etc. |
|
||||
<table>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th width='150'>Account</th>
|
||||
<th width='150'>Role</th>
|
||||
<th>Description</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-admin</code></td>
|
||||
<td><code>workspace-admin</code></td>
|
||||
<td>Manage all resources under the workspace (use this account to invite new members to the workspace).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>project-admin</code></td>
|
||||
<td><code>workspace-self-provisioner</code></td>
|
||||
<td>Create and manage projects and DevOps projects, and invite new members to join the projects.</td>
|
||||
</tr><tr>
|
||||
<td><code>project-regular</code></td>
|
||||
<td><code>workspace-viewer</code></td>
|
||||
<td><code>project-regular</code> will be invited by <code>project-admin</code> to join a project or DevOps project. The account can be used to create workloads, pipelines, etc.</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
### Step 3: Create a project
|
||||
|
||||
In this step, you create a project using the account `project-admin` created in the previous step. A project in KubeSphere is the same as a namespace in Kubernetes, which provides virtual isolation for resources. For more information, see [Namespaces](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/).
|
||||
|
||||
1. Log in to KubeSphere as `project-admin`. In **Projects**, click **Create**.
|
||||
|
||||
|
||||
1. Log in to the KubeSphere web console as `project-admin`. In **Projects**, click **Create**.
|
||||
|
||||
2. Enter the project name (for example, `demo-project`) and click **OK** to finish. You can also add an alias and description for the project.
|
||||
|
||||
|
||||
3. In **Projects**, click the project name to view its details page.
|
||||
|
||||
3. In **Projects**, click the project created just now to view its detailed information.
|
||||
4. On the **Overview** page of the project, the project quota remains unset by default. You can click **Set** and specify [resource requests and limits](../../workspace-administration/project-quotas/) as needed (for example, 1 Core for CPU and 1000 Gi for memory).
|
||||
|
||||
|
||||
|
||||
|
||||
4. On the **Overview** page of the project, the project quota remains unset by default. You can click **Set** and specify [resource requests and limits](../../workspace-administration/project-quotas/) as needed (for example, 1 core for CPU and 1000Gi for memory).
|
||||
5. Invite `project-regular` to this project and grant this user the role `operator`. Refer to the following image for specific steps.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
5. Invite `project-regular` to this project and grant this user the role `operator`. Refer to the image below for specific steps.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice info >}}
|
||||
The user granted the role `operator` will be a project maintainer who can manage resources other than users and roles in the project.
|
||||
The user granted the role `operator` is a project maintainer who can manage resources other than users and roles in the project.
|
||||
{{</ notice >}}
|
||||
|
||||
6. Before creating a [Route](../../project-user-guide/application-workloads/routes/) which is [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/) in Kubernetes, you need to enable a gateway for this project. The gateway is an [NGINX Ingress controller](https://github.com/kubernetes/ingress-nginx) running in the project. 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.
|
||||
|
||||
|
||||
7. Select the access method **NodePort** and click **Save**.
|
||||
|
||||
7. Choose the access method **NodePort** and click **Save**.
|
||||
|
||||
|
||||
|
||||
8. Under **Internet Access**, it can be seen that the Gateway Address and the NodePort of http and https all display on the page.
|
||||
8. Under **Internet Access**, you can obtain the Gateway Address and the NodePort of http and https in the list.
|
||||
|
||||
{{< notice note >}}
|
||||
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 that you use [PorterLB](https://github.com/kubesphere/porter) as the LoadBalancer plugin.
|
||||
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 that you use [OpenELB](https://github.com/kubesphere/openelb) as the LoadBalancer plugin.
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 4: Create a role
|
||||
|
||||
After you finish the above steps, you know that users can be granted different roles at different levels. The roles used in previous steps are all built-in ones created by KubeSphere itself. In this step, you will learn how to define a customized role to meet the needs in your work.
|
||||
After you finish the above steps, you know that users can be granted different roles at different levels. The roles used in previous steps are all built-in ones created by KubeSphere. In this step, you will learn how to define a customized role to meet the needs in your work.
|
||||
|
||||
1. Log in to the KubeSphere web console as `admin` again and go to **Access Control**.
|
||||
|
||||
2. Click **Account Roles** on the left navigation bar and **Create** on the right.
|
||||
2. Click **Account Roles** on the left navigation pane, and then click **Create** on the right.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -206,7 +225,7 @@ After you finish the above steps, you know that users can be granted different r
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
5. On the **Account Roles** page, you can click the name of the created role to view the role details and click <img src="/images/docs/quickstart/create-workspaces-projects-accounts/operation-icon.png" width="20px" align="center"> to edit or delete the role.
|
||||
5. On the **Account Roles** page, you can click the name of the created role to view the role details and click <img src="/images/docs/quickstart/create-workspaces-projects-accounts/operation-icon.png" width="20px" align="center"> to edit the role, edit the role permissions, or delete the role.
|
||||
|
||||
6. On the **Accounts** page, you can assign the role to an account when you create an account or edit an existing account.
|
||||
|
||||
|
|
@ -221,18 +240,12 @@ To create a DevOps project, you must install the KubeSphere DevOps system in adv
|
|||
|
||||
1. Log in to the console as `project-admin`. In **DevOps Projects**, click **Create**.
|
||||
|
||||
|
||||
2. Set a name for the DevOps project (for example, `demo-devops`) and click **OK**. You can also add an alias and description for the project.
|
||||
|
||||
2. Enter the DevOps project name (for example, `demo-devops`) and click **OK**. You can also add an alias and description for the project.
|
||||
3. Click the project name to view its details page.
|
||||
|
||||
|
||||
4. Go to **Project Management** and select **Project Members**. Click **Invite Member** to grant `project-regular` the role `operator`, who is allowed to create pipelines and credentials. Click **OK** to finish.
|
||||
|
||||
3. In **DevOps Projects**, click the project created just now to view its detailed information.
|
||||
|
||||
|
||||
|
||||
4. 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.
|
||||
|
||||
|
||||
|
||||
|
||||
You are now familiar with the multi-tenant management system of KubeSphere. In other tutorials, the account `project-regular` will also be used to demonstrate how to create applications and resources in a project or DevOps project.
|
||||
|
|
|
|||
|
|
@ -66,7 +66,7 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
3. 在**帐户管理**中，点击**创建**。在弹出的对话框中，提供所有必要信息（带有*标记），然后在**角色**一栏选择 `users-manager`。请参考下图示例。
|
||||
|
||||
|
||||
|
||||
|
||||
完成后，点击**确定**。新创建的帐户将显示在**帐户管理**中的帐户列表中。
|
||||
|
||||
|
|
@ -76,16 +76,37 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
帐户登出请点击右上角的用户名，然后选择**登出**。
|
||||
{{</ notice >}}
|
||||
|
||||
| 帐户 | 角色 | 描述 |
|
||||
| ----------------- | -------------------- | ------------------------------------------------------------ |
|
||||
| `ws-manager` | `workspaces-manager` | 创建和管理所有企业空间。 |
|
||||
| `ws-admin` | `platform-regular` | 管理指定企业空间中的所有资源（在此示例中，此帐户用于邀请新成员加入该企业空间）。 |
|
||||
| `project-admin` | `platform-regular` | 创建和管理项目以及 DevOps 工程，并邀请新成员加入项目。 |
|
||||
| `project-regular` | `platform-regular` | `project-regular` 将由 `project-admin` 邀请至项目或 DevOps 工程。该帐户将用于在指定项目中创建工作负载、流水线和其他资源。 |
|
||||
<table>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th width='140'>帐户</th>
|
||||
<th width='160'>角色</th>
|
||||
<th>描述</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-manager</code></td>
|
||||
<td><code>workspaces-manager</code></td>
|
||||
<td>创建和管理所有企业空间。</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-admin</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td>管理指定企业空间中的所有资源（在此示例中，此帐户用于邀请新成员加入该企业空间）。</td>
|
||||
</tr><tr>
|
||||
<td><code>project-admin</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td>创建和管理项目以及 DevOps 工程，并邀请新成员加入项目。</td>
|
||||
</tr><tr>
|
||||
<td><code>project-regular</code></td>
|
||||
<td><code>platform-regular</code></td>
|
||||
<td><code>project-regular</code> 将由 <code>project-admin</code> 邀请至项目或 DevOps 工程。该帐户将用于在指定项目中创建工作负载、流水线和其他资源。</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
5. 查看创建的四个帐户。
|
||||
|
||||
|
||||
|
||||
|
||||
### 步骤 2：创建企业空间
|
||||
|
||||
|
|
@ -93,13 +114,7 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
1. 以 `ws-manager` 身份登录 KubeSphere，它具有管理平台上所有企业空间的权限。点击左上角的**平台管理**，选择**访问控制**。在**企业空间**中，可以看到仅列出了一个默认企业空间 `system-workspace`，即系统企业空间，其中运行着与系统相关的组件和服务，您无法删除该企业空间。
|
||||
|
||||
|
||||
|
||||
2. 点击右侧的**创建**，将新企业空间命名为 `demo-workspace`，并将用户 `ws-admin` 设置为企业空间管理员，如下图所示：
|
||||
|
||||
|
||||
|
||||
完成后，点击**创建**。
|
||||
2. 点击右侧的**创建**，将新企业空间命名为 `demo-workspace`，并将用户 `ws-admin` 设置为企业空间管理员。完成后，点击**创建**。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -109,49 +124,57 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
3. 登出控制台，然后以 `ws-admin` 身份重新登录。在**企业空间设置**中，选择**企业成员**，然后点击**邀请成员**。
|
||||
|
||||
|
||||
|
||||
4. 邀请 `project-admin` 和 `project-regular` 进入企业空间，分别授予他们 `workspace-self-provisioner` 和 `workspace-viewer` 角色。
|
||||
4. 邀请 `project-admin` 和 `project-regular` 进入企业空间，分别授予 `workspace-self-provisioner` 和 `workspace-viewer` 角色，点击**确定**。
|
||||
|
||||
{{< notice note >}}
|
||||
实际角色名称的格式：`<workspace name>-<role name>`。例如，在名为 `demo-workspace` 的企业空间中，角色 `viewer` 的实际角色名称为 `demo-workspace-viewer`。
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
5. 将 `project-admin` 和 `project-regular` 都添加到企业空间后，点击**确定**。在**企业成员**中，您可以看到列出的三名成员。
|
||||
|
||||
| 帐户 | 角色 | 描述 |
|
||||
| ----------------- | ---------------------------- | ------------------------------------------------------------ |
|
||||
| `ws-admin` | `workspace-admin` | 管理指定企业空间中的所有资源（在此示例中，此帐户用于邀请新成员加入企业空间）。 |
|
||||
| `project-admin` | `workspace-self-provisioner` | 创建和管理项目以及 DevOps 工程，并邀请新成员加入项目。 |
|
||||
| `project-regular` | `workspace-viewer` | `project-regular` 将由 `project-admin` 邀请至项目或 DevOps 工程。该帐户将用于在指定项目中创建工作负载、流水线和其他资源。 |
|
||||
<table>
|
||||
<tbody>
|
||||
<tr>
|
||||
<th width='150'>帐户</th>
|
||||
<th width='150'>角色</th>
|
||||
<th>描述</th>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>ws-admin</code></td>
|
||||
<td><code>workspace-admin</code></td>
|
||||
<td>管理指定企业空间中的所有资源（在此示例中，此帐户用于邀请新成员加入企业空间）。</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td><code>project-admin</code></td>
|
||||
<td><code>workspace-self-provisioner</code></td>
|
||||
<td>创建和管理项目以及 DevOps 工程，并邀请新成员加入项目。</td>
|
||||
</tr><tr>
|
||||
<td><code>project-regular</code></td>
|
||||
<td><code>workspace-viewer</code></td>
|
||||
<td><code>project-regular</code> 将由 <code>project-admin</code> 邀请至项目或 DevOps 工程。该帐户将用于在指定项目中创建工作负载、流水线和其他资源。</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
### 步骤 3：创建项目
|
||||
|
||||
在此步骤中，您需要使用在上一步骤中创建的帐户 `project-admin` 来创建项目。KubeSphere 中的项目与 Kubernetes 中的命名空间相同，为资源提供了虚拟隔离。有关更多信息，请参见[命名空间](https://kubernetes.io/zh/docs/concepts/overview/working-with-objects/namespaces/)。
|
||||
|
||||
1. 以 `project-admin` 身份登录 KubeSphere，在**项目管理**中，点击**创建**。
|
||||
|
||||
|
||||
1. 以 `project-admin` 身份登录 KubeSphere Web 控制台，在**项目管理**中，点击**创建**。
|
||||
|
||||
2. 输入项目名称（例如 `demo-project`），然后点击**确定**完成，您还可以为项目添加别名和描述。
|
||||
|
||||
|
||||
|
||||
3. 在**项目管理**中，点击刚创建的项目查看其详细信息。
|
||||
|
||||
|
||||
3. 在**项目管理**中，点击刚创建的项目查看其详情页面。
|
||||
|
||||
4. 在项目的**概览**页面，默认情况下未设置项目配额。您可以点击**设置**并根据需要指定[资源请求和限制](../../workspace-administration/project-quotas/)（例如：CPU 和内存的限制分别设为 1 Core 和 1000 Gi）。
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
5. 邀请 `project-regular` 至该项目，并授予该用户 `operator` 角色。请参考下图以了解具体步骤。
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice info >}}
|
||||
具有 `operator` 角色的用户是项目维护者，可以管理项目中除用户和角色以外的资源。
|
||||
|
|
@ -159,19 +182,15 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
6. 在创建[应用路由](../../project-user-guide/application-workloads/routes/)（即 Kubernetes 中的 [Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)）之前，需要启用该项目的网关。网关是在项目中运行的 [NGINX Ingress 控制器](https://github.com/kubernetes/ingress-nginx)。若要设置网关，请转到**项目设置**中的**高级设置**，然后点击**设置网关**。此步骤中仍使用帐户 `project-admin`。
|
||||
|
||||
|
||||
|
||||
7. 选择访问方式 **NodePort**，然后点击**保存**。
|
||||
|
||||
|
||||
|
||||
8. 在**外网访问**下，可以在页面上看到网关地址以及 http/https 的端口。
|
||||
|
||||
{{< notice note >}}
|
||||
如果要使用 `LoadBalancer` 暴露服务，则需要使用云厂商的 LoadBalancer 插件。如果您的 Kubernetes 集群在裸机环境中运行，建议使用 [PorterLB](https://github.com/kubesphere/porter) 作为 LoadBalancer 插件。
|
||||
如果要使用 `LoadBalancer` 暴露服务，则需要使用云厂商的 LoadBalancer 插件。如果您的 Kubernetes 集群在裸机环境中运行，建议使用 [OpenELB](https://github.com/kubesphere/openelb) 作为 LoadBalancer 插件。
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
### 步骤 4：创建角色
|
||||
|
||||
|
|
@ -206,7 +225,7 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
5. 在**帐户角色**页面，可以点击所创建角色的名称查看角色详情，点击 <img src="/images/docs/zh-cn/quickstart/create-workspaces-projects-accounts/operation-icon.png" width="20px" align="center"> 以编辑或删除该角色。
|
||||
5. 在**帐户角色**页面，可以点击所创建角色的名称查看角色详情，点击 <img src="/images/docs/zh-cn/quickstart/create-workspaces-projects-accounts/操作按钮.png" width="20px" align="center" /> 以编辑角色、编辑角色权限或删除该角色。
|
||||
|
||||
6. 在**帐户管理**页面，可以在创建帐户或编辑现有帐户时为帐户分配该角色。
|
||||
|
||||
|
|
@ -220,18 +239,12 @@ KubeSphere 的多租户系统分**三个**层级，即集群、企业空间和
|
|||
|
||||
1. 以 `project-admin` 身份登录控制台，在 **DevOps 工程**中，点击**创建**。
|
||||
|
||||
|
||||
|
||||
2. 输入 DevOps 工程名称（例如 `demo-devops`），然后点击**确定**，也可以为该工程添加别名和描述。
|
||||
|
||||
|
||||
|
||||
3. 在 **DevOps 工程**中，点击刚创建的工程查看其详细信息。
|
||||
|
||||
|
||||
3. 点击刚创建的工程查看其详细页面。
|
||||
|
||||
4. 转到**工程管理**，然后选择**工程成员**。点击**邀请成员**授予 `project-regular` 用户 `operator` 的角色，允许其创建流水线和凭证。
|
||||
|
||||
|
||||
|
||||
|
||||
至此，您已熟悉 KubeSphere 的多租户管理系统。在其他教程中，`project-regular` 帐户还将用于演示如何在项目或 DevOps 工程中创建应用程序和资源。
|
||||
|
|
|
|||
Binary file not shown.
|
After Width: | Height: | Size: 349 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.2 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 254 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.2 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 285 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 2.1 KiB After Width: | Height: | Size: 1.6 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 181 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 132 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 124 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 132 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 114 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 158 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 220 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 175 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 115 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 673 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 119 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 129 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.0 MiB |
Binary file not shown.
|
Before Width: | Height: | Size: 186 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 1.6 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 134 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 416 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 245 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 235 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 211 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 140 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 159 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 98 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 111 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 362 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 268 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 287 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 172 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 378 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 193 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 122 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 209 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 178 KiB |
Loading…
Reference in New Issue