Merge branch 'master' into update-graphical-pipeline
Felixnoo
GitHub
|
|
@ -31,35 +31,35 @@ In **Project Roles**, there are three available built-in roles as shown below. B
|
|||
|
||||
## Create a DevOps Project Role
|
||||
|
||||
1. Log in to the console as `devops-admin` and select a DevOps project (for example, `demo-devops`) under **DevOps Projects** list.
|
||||
1. Log in to the console as `devops-admin` and select a DevOps project (for example, `demo-devops`) on the **DevOps Projects** page.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
The account `devops-admin` is used as an example. As long as the account you are using is granted a role including the authorization of **Project Members View**, **Project Roles Management** and **Project Roles View** in **Access Control** at DevOps project level, it can create a DevOps project role.
|
||||
The account `devops-admin` is used as an example. As long as the account you are using is granted a role including the permissions of **Project Member Viewing**, **Project Role Management** and **Project Role Viewing** in **Access Control** at DevOps project level, it can create a DevOps project role.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
2. Go to **Project Roles** in **Project Management**, click **Create** and set a **Role Identifier**. In this example, a role named `pipeline-creator` will be created. Click **Edit Authorization** to continue.
|
||||
2. Go to **Project Roles** in **Project Management**, click **Create** and set a **Name**. In this example, a role named `pipeline-creator` will be created. Click **Edit Permissions** to continue.
|
||||
|
||||
|
||||
|
||||
3. In **Pipelines Management**, select the authorization that you want this role to contain. For example, **Pipelines Management** and **Pipelines View** are selected for this role. Click **OK** to finish.
|
||||
3. In **Pipeline Management**, select the permissions that you want this role to contain. For example, **Pipeline Management** and **Pipeline Viewing** are selected for this role. Click **OK** to finish.
|
||||
|
||||
|
||||
|
||||
{{< notice 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.
|
||||
**Depends on** means the major permission (the one listed after **Depends on**) needs to be selected first so that the affiliated permission can be assigned.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
4. Newly-created roles will be listed in **Project Roles**. You can click the three dots on the right to edit it.
|
||||
4. Newly created roles will be listed in **Project Roles**. You can click <img src="/images/docs/devops-user-guide/understand-and-manage-devops-projects/role-and-member-management/three-dots.png" height="15px"> on the right to edit it.
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
The role of `pipeline-creator` is only granted **Pipelines Management** and **Pipelines View**, which may not satisfy your need. This example is only for demonstration purpose. You can create customized roles based on your needs.
|
||||
The role of `pipeline-creator` is only granted **Pipeline Management** and **Pipeline Viewing**, which may not satisfy your need. This example is only for demonstration purpose. You can create customized roles based on your needs.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -67,7 +67,7 @@ In **Project Roles**, there are three available built-in roles as shown below. B
|
|||
|
||||
1. In **Project Management**, select **Project Members** and click **Invite Member**.
|
||||
|
||||
2. Invite a user to the DevOps project. Grant the role of `pipeline-creator` to the user.
|
||||
2. Click <img src="/images/docs/devops-user-guide/understand-and-manage-devops-projects/role-and-member-management/plus-button.png" height="15px"> to invite an account to the DevOps project. Grant the role of `pipeline-creator` to the account.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,7 +2,7 @@
|
|||
title: 'KubeSphere 部署 Litmus 至 Kubernetes 开启混沌实验'
|
||||
tag: 'Litmus,KubeSphere'
|
||||
keywords: 'Litmus,LitmusChaos,Kubernetes,Helm,KubeSphere'
|
||||
description: Litmus 是一种开源的云原生混沌工程工具集，专注于 Kubernetes 集群进行模拟故障测试，以帮助开发者和 SRE 发现集群及程序中的缺陷，从而提高系统的健壮性。本文介绍了 Litmus 的架构以及在 KubeSphere 上的部署方法，通过一系列混沌实验来验证整个基础设施和服务抵抗故障的能力。'
|
||||
description: 'Litmus 是一种开源的云原生混沌工程工具集，专注于 Kubernetes 集群进行模拟故障测试，以帮助开发者和 SRE 发现集群及程序中的缺陷，从而提高系统的健壮性。本文介绍了 Litmus 的架构以及在 KubeSphere 上的部署方法，通过一系列混沌实验来验证整个基础设施和服务抵抗故障的能力。'
|
||||
createTime: '2021-06-09'
|
||||
author: '杨传胜'
|
||||
snapshot: 'https://pek3b.qingstor.com/kubesphere-community/images/20210609224203.png'
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ weight: 11130
|
|||
|
||||
## 创建 DevOps 工程角色
|
||||
|
||||
1. 以 `devops-admin` 身份登录控制台，然后在 **DevOps 工程**列表下选择一个 DevOps 工程（例如 `demo-devops`）。
|
||||
1. 以 `devops-admin` 身份登录控制台，然后前往 **DevOps 工程**页面选择一个 DevOps 工程（例如 `demo-devops`）。
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -41,21 +41,21 @@ weight: 11130
|
|||
|
||||
2. 转到**工程管理**中的**工程角色**，点击**创建**并设置**角色标识符**。在本示例中，将创建一个名为 `pipeline-creator` 的角色。点击**编辑权限**继续。
|
||||
|
||||
|
||||
|
||||
|
||||
3. 在**流水线管理**中，选择您希望授予该角色的权限。例如，为此角色选择了**流水线管理**和**流水线查看**。点击**确定**完成操作。
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
**依赖于**表示首先需要选择主要授权（**依赖于**之后列出的），以便可以分配关联授权。
|
||||
**依赖于**表示首先需要选择主要权限（**依赖于**之后列出的），以便可以分配关联权限。
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
4. 新创建的角色将列在**工程角色**中。您可以点击右侧的三个点对其进行编辑。
|
||||
4. 新创建的角色将列在**工程角色**中。您可以点击右侧的 <img src="/images/docs/zh-cn/devops-user-guide/understand-and-manage-devops-projects/role-and-member-management/three-dots.png" height="15px"> 对其进行编辑。
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -67,9 +67,9 @@ weight: 11130
|
|||
|
||||
1. 在**工程管理**中选择**工程成员**，然后点击**邀请成员**。
|
||||
|
||||
2. 邀请用户加入此 DevOps 工程，并向此用户授予 `pipeline-creator` 角色。
|
||||
2. 点击 <img src="/images/docs/zh-cn/devops-user-guide/understand-and-manage-devops-projects/role-and-member-management/plus-button.png" height="15px"> 邀请帐户加入此 DevOps 工程，并向此帐户授予 `pipeline-creator` 角色。
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -81,5 +81,5 @@ weight: 11130
|
|||
|
||||
4. 您还可以通过编辑现有成员来更改其角色或将其从 DevOps 工程中删除。
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@
|
|||
{{ if eq .Site.Language.Lang "en"}}
|
||||
<div class="join-div">
|
||||
<div class="content">
|
||||
🚀 KubeSphere 3.1.0 is now general available！It extends the Kubernetes from the multi-cloud to the edge. <a href={{"/docs/release/release-v310/" | relLangURL }} target="_blank" rel="noopener noreferrer">Read the Release Notes for 3.1.0 →</a>
|
||||
🚀 KubeSphere 3.1.0 is now generally available as it extends Kubernetes from the cloud to the edge. <a href={{"/docs/release/release-v310/" | relLangURL }} target="_blank" rel="noopener noreferrer">Read the Release Notes for 3.1.0 →</a>
|
||||
<img id="close-join" src="/images/header/close.svg" alt="close">
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
Before Width: | Height: | Size: 105 KiB After Width: | Height: | Size: 158 KiB |
|
Before Width: | Height: | Size: 94 KiB After Width: | Height: | Size: 238 KiB |
|
Before Width: | Height: | Size: 93 KiB After Width: | Height: | Size: 270 KiB |
|
Before Width: | Height: | Size: 56 KiB After Width: | Height: | Size: 150 KiB |
|
Before Width: | Height: | Size: 86 KiB After Width: | Height: | Size: 642 KiB |
|
After Width: | Height: | Size: 9.6 KiB |
|
After Width: | Height: | Size: 1.4 KiB |
|
Before Width: | Height: | Size: 113 KiB |
|
After Width: | Height: | Size: 418 KiB |
|
Before Width: | Height: | Size: 77 KiB |
|
After Width: | Height: | Size: 235 KiB |
|
Before Width: | Height: | Size: 87 KiB |
|
Before Width: | Height: | Size: 50 KiB |
|
After Width: | Height: | Size: 262 KiB |
|
After Width: | Height: | Size: 150 KiB |
|
Before Width: | Height: | Size: 94 KiB |
|
After Width: | Height: | Size: 255 KiB |
|
After Width: | Height: | Size: 9.6 KiB |
|
After Width: | Height: | Size: 1.4 KiB |