mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Change doc URL form docs to docs/v3.3
Signed-off-by: Patrick-LuoYu <patrickluo@yunify.com>
This commit is contained in:
Patrick-LuoYu
parent
478df653f0
commit
bd1b2549a1
|
|
@ -389,7 +389,7 @@ section {
|
|||
z-index: 2;
|
||||
width: 20px;
|
||||
height: 20px;
|
||||
background-image: url('/images/docs/copy.png');
|
||||
background-image: url('/images/docs/v3.3/copy.png');
|
||||
background-repeat: no-repeat;
|
||||
background-size: cover;
|
||||
cursor: pointer;
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ main {
|
|||
position: relative;
|
||||
padding-top: 129px;
|
||||
padding-bottom: 20px;
|
||||
background-image: url("/images/docs/banner.png");
|
||||
background-image: url("/images/docs/v3.3/banner.png");
|
||||
|
||||
.common-layout {
|
||||
position: relative;
|
||||
|
|
@ -272,14 +272,14 @@ main {
|
|||
width: 12px;
|
||||
height: 11px;
|
||||
background-repeat: no-repeat;
|
||||
background-image: url("/images/docs/downgrade.svg");
|
||||
background-image: url("/images/docs/v3.3/downgrade.svg");
|
||||
}
|
||||
|
||||
&:hover {
|
||||
color: #56bc8a;
|
||||
|
||||
.download-icon {
|
||||
background-image: url("/images/docs/downgrade-hover.svg");
|
||||
background-image: url("/images/docs/v3.3/downgrade-hover.svg");
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -362,14 +362,14 @@ main {
|
|||
|
||||
.edit-div {
|
||||
.icon-span {
|
||||
background-image: url("/images/docs/edit.svg");
|
||||
background-image: url("/images/docs/v3.3/edit.svg");
|
||||
}
|
||||
|
||||
&:hover {
|
||||
color: #56bc8a;
|
||||
|
||||
.icon-span {
|
||||
background-image: url("/images/docs/edit-hover.svg");
|
||||
background-image: url("/images/docs/v3.3/edit-hover.svg");
|
||||
}
|
||||
|
||||
a {
|
||||
|
|
@ -382,12 +382,12 @@ main {
|
|||
.icon-span {
|
||||
color: #56bc8a;
|
||||
|
||||
background-image: url("/images/docs/feedback.svg");
|
||||
background-image: url("/images/docs/v3.3/feedback.svg");
|
||||
}
|
||||
|
||||
&:hover {
|
||||
.icon-span {
|
||||
background-image: url("/images/docs/feedback-hover.svg");
|
||||
background-image: url("/images/docs/v3.3/feedback-hover.svg");
|
||||
}
|
||||
|
||||
a {
|
||||
|
|
@ -400,14 +400,14 @@ main {
|
|||
position: relative;
|
||||
|
||||
.icon-span {
|
||||
background-image: url("/images/docs/share.svg");
|
||||
background-image: url("/images/docs/v3.3/share.svg");
|
||||
}
|
||||
|
||||
&:hover {
|
||||
color: #56bc8a;
|
||||
|
||||
.icon-span {
|
||||
background-image: url("/images/docs/share-hover.svg");
|
||||
background-image: url("/images/docs/v3.3/share-hover.svg");
|
||||
}
|
||||
|
||||
ul {
|
||||
|
|
|
|||
|
|
@ -55,7 +55,7 @@
|
|||
background-color: #36435c;
|
||||
background-repeat: no-repeat;
|
||||
background-position: left bottom;
|
||||
background-image: url("/images/docs/26.svg");
|
||||
background-image: url("/images/docs/v3.3/26.svg");
|
||||
|
||||
@media only screen and (max-width: $mobile-max-width) {
|
||||
display: block;
|
||||
|
|
@ -130,10 +130,10 @@
|
|||
display: inline-block;
|
||||
width: 40px;
|
||||
height: 40px;
|
||||
background-image: url("/images/docs/22.svg");
|
||||
background-image: url("/images/docs/v3.3/22.svg");
|
||||
|
||||
&:hover {
|
||||
background-image: url("/images/docs/22-hover.svg");
|
||||
background-image: url("/images/docs/v3.3/22-hover.svg");
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -221,15 +221,15 @@
|
|||
}
|
||||
|
||||
& > li:nth-child(3n + 1) {
|
||||
background-image: url("/images/docs/bg-1.svg");
|
||||
background-image: url("/images/docs/v3.3/bg-1.svg");
|
||||
}
|
||||
|
||||
& > li:nth-child(3n + 2) {
|
||||
background-image: url("/images/docs/bg-2.svg");
|
||||
background-image: url("/images/docs/v3.3/bg-2.svg");
|
||||
}
|
||||
|
||||
& > li:nth-child(3n + 3) {
|
||||
background-image: url("/images/docs/bg-3.svg");
|
||||
background-image: url("/images/docs/v3.3/bg-3.svg");
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
@ -318,7 +318,7 @@
|
|||
background-position: center;
|
||||
background-size: cover;
|
||||
background-color: #ffffff;
|
||||
background-image: url('/images/docs/bg-line.png');
|
||||
background-image: url('/images/docs/v3.3/bg-line.png');
|
||||
|
||||
@media only screen and (max-width: $mobile-max-width) {
|
||||
position: relative;
|
||||
|
|
|
|||
|
|
@ -106,43 +106,48 @@ hasChildren = true
|
|||
weight = 4
|
||||
name = "Documentation"
|
||||
hasChildren = true
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v3.2.x <img src='/images/header/star.svg' alt='star'>"
|
||||
URL = "/docs"
|
||||
name = "v3.3 <img src='/images/header/star.svg' alt='star'>"
|
||||
URL = "/docs/v3.3"
|
||||
weight = 1
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v3.1.x"
|
||||
URL = "https://v3-1.docs.kubesphere.io/docs"
|
||||
name = "v3.2"
|
||||
URL = "/docs"
|
||||
weight = 2
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v3.0.0"
|
||||
URL = "https://v3-0.docs.kubesphere.io/docs"
|
||||
name = "v3.1"
|
||||
URL = "https://v3-1.docs.kubesphere.io/docs"
|
||||
weight = 3
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v2.1.x"
|
||||
URL = "https://v2-1.docs.kubesphere.io/docs"
|
||||
name = "v3.0"
|
||||
URL = "https://v3-0.docs.kubesphere.io/docs"
|
||||
weight = 4
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v2.0.x"
|
||||
URL = "https://v2-0.docs.kubesphere.io/docs/"
|
||||
name = "v2.1"
|
||||
URL = "https://v2-1.docs.kubesphere.io/docs"
|
||||
weight = 5
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v1.0.0"
|
||||
URL = "https://v1-0.docs.kubesphere.io/docs/"
|
||||
name = "v2.0"
|
||||
URL = "https://v2-0.docs.kubesphere.io/docs/"
|
||||
weight = 6
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
parent = "Documentation"
|
||||
name = "v1.0"
|
||||
URL = "https://v1-0.docs.kubesphere.io/docs/"
|
||||
weight = 7
|
||||
|
||||
[[languages.en.menu.main]]
|
||||
weight = 5
|
||||
hasChildren = true
|
||||
|
|
|
|||
|
|
@ -115,25 +115,25 @@ section4:
|
|||
- name: App Store
|
||||
icon: /images/home/store.svg
|
||||
content: Provide an application store for Helm-based applications, and offer application lifecycle management on Kubernetes platform
|
||||
link: "/docs/pluggable-components/app-store/"
|
||||
link: "/docs/v3.3/pluggable-components/app-store/"
|
||||
color: grape
|
||||
|
||||
- name: Kubernetes Multi-cluster Mgmt
|
||||
icon: /images/home/management.svg
|
||||
content: Distribute applications across multiple clusters and cloud providers, and provide disaster recovery solutions and cross-cluster observability
|
||||
link: "/docs/multicluster-management/introduction/overview/"
|
||||
link: "/docs/v3.3/multicluster-management/introduction/overview/"
|
||||
color: orange
|
||||
|
||||
- name: Edge Computing Platform
|
||||
icon: /images/home/multiple.svg
|
||||
content: KubeSphere integrates <a class='inner-a' target='_blank' href='https://kubeedge.io/en/'>KubeEdge</a> to enable users to deploy applications on the edge devices and view logging and monitoring data of them on the console.
|
||||
link: "/docs/pluggable-components/kubeedge/"
|
||||
link: "/docs/v3.3/pluggable-components/kubeedge/"
|
||||
color: grape
|
||||
|
||||
- name: Metering and Billing
|
||||
icon: /images/home/network.svg
|
||||
content: Track resource consumption at different levels on a unified dashboard, which helps you make better-informed decisions on planning and reduce the cost.
|
||||
link: "/docs/toolbox/metering-and-billing/view-resource-consumption/"
|
||||
link: "/docs/v3.3/toolbox/metering-and-billing/view-resource-consumption/"
|
||||
color: green
|
||||
|
||||
section5:
|
||||
|
|
|
|||
|
|
@ -93,7 +93,7 @@ If you already have an Okta account, you can skip this step, but you need to mak
|
|||
|
||||
### Step 4: Make configurations on KubeSphere
|
||||
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/common-icons/hammer.png" width="20" /> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/v3.3/common-icons/hammer.png" width="20" /> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
|
||||
```bash
|
||||
kubectl -n kubesphere-system edit cc ks-installer
|
||||
|
|
|
|||
|
|
@ -1,28 +0,0 @@
|
|||
---
|
||||
title: "Installing on Kubernetes"
|
||||
description: "Demonstrate how to install KubeSphere on Kubernetes either hosted on cloud or on-premises."
|
||||
layout: "second"
|
||||
|
||||
linkTitle: "Installing on Kubernetes"
|
||||
weight: 4000
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
---
|
||||
|
||||
This chapter demonstrates how to deploy KubeSphere on existing Kubernetes clusters hosted on cloud or on-premises. As a highly flexible solution to container orchestration, KubeSphere can be deployed across various Kubernetes engines.
|
||||
|
||||
## Most Popular Pages
|
||||
|
||||
Below you will find some of the most viewed and helpful pages in this chapter. It is highly recommended that you refer to them first.
|
||||
|
||||
{{< popularPage icon="/images/docs/brand-icons/gke.jpg" title="Deploy KubeSphere on GKE" description="Provision KubeSphere on existing Kubernetes clusters on GKE." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-gke/" >}}
|
||||
|
||||
{{< popularPage icon="/images/docs/bitmap.jpg" title="Deploy KubeSphere on AWS EKS" description="Provision KubeSphere on existing Kubernetes clusters on EKS." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-eks/" >}}
|
||||
|
||||
{{< popularPage icon="/images/docs/brand-icons/aks.jpg" title="Deploy KubeSphere on AKS" description="Provision KubeSphere on existing Kubernetes clusters on AKS." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-aks/" >}}
|
||||
|
||||
{{< popularPage icon="/images/docs/brand-icons/huawei.svg" title="Deploy KubeSphere on CCE" description="Provision KubeSphere on existing Kubernetes clusters on Huawei CCE." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce/" >}}
|
||||
|
||||
{{< popularPage icon="/images/docs/brand-icons/oracle.jpg" title="Deploy KubeSphere on Oracle OKE" description="Provision KubeSphere on existing Kubernetes clusters on OKE." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-oke/" >}}
|
||||
|
||||
{{< popularPage icon="/images/docs/brand-icons/digital-ocean.jpg" title="Deploy KubeSphere on DO" description="Provision KubeSphere on existing Kubernetes clusters on DigitalOcean." link="../installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-do/" >}}
|
||||
|
|
@ -8,7 +8,7 @@ LinkTitle: "Documentation"
|
|||
section1:
|
||||
title: KubeSphere Documentation
|
||||
content: Learn how to build and manage cloud-native applications using KubeSphere Container Platform. Get documentation, example code, tutorials, and more.
|
||||
image: /images/docs/banner.png
|
||||
image: /images/docs/v3.3/banner.png
|
||||
|
||||
sectionLink:
|
||||
docs:
|
||||
|
|
@ -45,13 +45,13 @@ section3:
|
|||
title: Run KubeSphere and Kubernetes Stack from the Cloud Service
|
||||
description: Cloud Providers are providing KubeSphere as a cloud-hosted service for users, helping you to create a highly available Kubernetes cluster managed by KubeSphere within minutes via several clicks. It enables you to use the cloud-hosted Kubernetes services out of the box.
|
||||
list:
|
||||
- image: /images/docs/aws.jpg
|
||||
- image: /images/docs/v3.3/aws.jpg
|
||||
content: AWS Quickstart
|
||||
link: https://aws.amazon.com/quickstart/architecture/qingcloud-kubesphere/
|
||||
- image: /images/docs/microsoft-azure.jpg
|
||||
- image: /images/docs/v3.3/microsoft-azure.jpg
|
||||
content: Azure Marketplace
|
||||
link: https://market.azure.cn/marketplace/apps/qingcloud.kubesphere
|
||||
- image: /images/docs/qingcloud.svg
|
||||
- image: /images/docs/v3.3/qingcloud.svg
|
||||
content: QingCloud QKE
|
||||
link: https://www.qingcloud.com/products/kubesphereqke/
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ layout: "second"
|
|||
linkTitle: "Access Control and Account Management"
|
||||
weight: 12000
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
icon: "/images/docs/v3.3/docs.svg"
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -13,11 +13,11 @@ weight: 12221
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/installing-on-linux/) and [Installing on Kubernetes](/docs/installing-on-kubernetes/).
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/v3.3/installing-on-linux/) and [Installing on Kubernetes](/docs/v3.3/installing-on-kubernetes/).
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/v3.3/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
|
||||
```bash
|
||||
kubectl -n kubesphere-system edit cc ks-installer
|
||||
|
|
@ -13,12 +13,12 @@ KubeSphere provides a built-in OAuth server. Users can obtain OAuth access token
|
|||
|
||||
## Prerequisites
|
||||
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/installing-on-linux/) and [Installing on Kubernetes](/docs/installing-on-kubernetes/).
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/v3.3/installing-on-linux/) and [Installing on Kubernetes](/docs/v3.3/installing-on-kubernetes/).
|
||||
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/v3.3/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
|
||||
```bash
|
||||
kubectl -n kubesphere-system edit cc ks-installer
|
||||
|
|
@ -11,12 +11,12 @@ This document describes how to use an LDAP service as an external identity provi
|
|||
|
||||
## Prerequisites
|
||||
|
||||
* You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/installing-on-linux/) and [Installing on Kubernetes](/docs/installing-on-kubernetes/).
|
||||
* You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/v3.3/installing-on-linux/) and [Installing on Kubernetes](/docs/v3.3/installing-on-kubernetes/).
|
||||
* You need to obtain the manager distinguished name (DN) and manager password of an LDAP service.
|
||||
|
||||
## Procedure
|
||||
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/v3.3/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
|
||||
```bash
|
||||
kubectl -n kubesphere-system edit cc ks-installer
|
||||
|
|
@ -10,11 +10,11 @@ This document describes how to use an external identity provider based on the OA
|
|||
|
||||
The following figure shows the authentication process between KubeSphere and an external OAuth 2.0 identity provider.
|
||||
|
||||
|
||||
|
||||
|
||||
## Prerequisites
|
||||
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/installing-on-linux/) and [Installing on Kubernetes](/docs/installing-on-kubernetes/).
|
||||
You need to deploy a Kubernetes cluster and install KubeSphere in the cluster. For details, see [Installing on Linux](/docs/v3.3/installing-on-linux/) and [Installing on Kubernetes](/docs/v3.3/installing-on-kubernetes/).
|
||||
|
||||
## Develop an OAuth 2.0 Plugin
|
||||
|
||||
|
|
@ -81,7 +81,7 @@ KubeSphere provides two built-in OAuth 2.0 plugins: [GitHubIdentityProvider](htt
|
|||
|
||||
## Integrate an Identity Provider with KubeSphere
|
||||
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
1. Log in to KubeSphere as `admin`, move the cursor to <img src="/images/docs/v3.3/access-control-and-account-management/external-authentication/set-up-external-authentication/toolbox.png" width="20px" height="20px"> in the lower-right corner, click **kubectl**, and run the following command to edit `ks-installer` of the CRD `ClusterConfiguration`:
|
||||
|
||||
```bash
|
||||
kubectl -n kubesphere-system edit cc ks-installer
|
||||
|
|
@ -126,5 +126,5 @@ KubeSphere provides two built-in OAuth 2.0 plugins: [GitHubIdentityProvider](htt
|
|||
|
||||
6. On the login page of the external identity provider, enter the username and password of a user configured at the identity provider to log in to KubeSphere.
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ The isolation of physical resources includes nodes and networks, while it also r
|
|||
|
||||
To solve the issues above, KubeSphere provides a multi-tenant management solution based on Kubernetes.
|
||||
|
||||
|
||||
|
||||
|
||||
In KubeSphere, the [workspace](../../workspace-administration/what-is-workspace/) is the smallest tenant unit. A workspace enables users to share resources across clusters and projects. Workspace members can create projects in an authorized cluster and invite other members to cooperate in the same project.
|
||||
|
||||
|
|
@ -38,9 +38,9 @@ Similar to Kubernetes, KubeSphere uses RBAC to manage permissions granted to use
|
|||
|
||||
The access control in KubeSphere is divided into three levels: platform, workspace and project. You use roles to control what permissions users have at different levels for different resources.
|
||||
|
||||
1. [Platform roles](/docs/quick-start/create-workspace-and-project/): Control what permissions platform users have for platform resources, such as clusters, workspaces and platform members.
|
||||
2. [Workspace roles](/docs/workspace-administration/role-and-member-management/): Control what permissions workspace members have for workspace resources, such as projects (i.e. namespaces) and DevOps projects.
|
||||
3. [Project roles](/docs/project-administration/role-and-member-management/): Control what permissions project members have for project resources, such as workloads and pipelines.
|
||||
1. [Platform roles](/docs/v3.3/quick-start/create-workspace-and-project/): Control what permissions platform users have for platform resources, such as clusters, workspaces and platform members.
|
||||
2. [Workspace roles](/docs/v3.3/workspace-administration/role-and-member-management/): Control what permissions workspace members have for workspace resources, such as projects (i.e. namespaces) and DevOps projects.
|
||||
3. [Project roles](/docs/v3.3/project-administration/role-and-member-management/): Control what permissions project members have for project resources, such as workloads and pipelines.
|
||||
|
||||
### Network isolation
|
||||
|
||||
|
|
@ -54,4 +54,4 @@ KubeSphere also provides [auditing logs](../../pluggable-components/auditing-log
|
|||
|
||||
For a complete authentication and authorization chain in KubeSphere, see the following diagram. KubeSphere has expanded RBAC rules using the Open Policy Agent (OPA). The KubeSphere team looks to integrate [Gatekeeper](https://github.com/open-policy-agent/gatekeeper) to provide more security management policies.
|
||||
|
||||
|
||||
|
||||
|
|
@ -7,7 +7,7 @@ layout: "second"
|
|||
linkTitle: "App Store"
|
||||
weight: 14000
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
icon: "/images/docs/v3.3/docs.svg"
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -132,7 +132,7 @@ After the app is approved, `isv` can release the Redis application to the App St
|
|||
|
||||
`app-reviewer` can create multiple categories for different types of applications based on their function and usage. It is similar to setting tags and categories can be used in the App Store as filters, such as Big Data, Middleware, and IoT.
|
||||
|
||||
1. Log in to KubeSphere as `app-reviewer`. To create a category, go to the **App Store Management** page and click <img src="/images/docs/appstore/application-lifecycle-management/plus.png" height="20px"> in **App Categories**.
|
||||
1. Log in to KubeSphere as `app-reviewer`. To create a category, go to the **App Store Management** page and click <img src="/images/docs/v3.3/appstore/application-lifecycle-management/plus.png" height="20px"> in **App Categories**.
|
||||
|
||||
2. Set a name and icon for the category in the dialog, then click **OK**. For Redis, you can enter `Database` for the field **Name**.
|
||||
|
||||
|
|
@ -8,13 +8,13 @@ linkTitle: "Deploy Chaos Mesh on KubeSphere"
|
|||
|
||||
[Chaos Mesh](https://github.com/chaos-mesh/chaos-mesh) is a cloud-native Chaos Engineering platform that orchestrates chaos in Kubernetes environments. With Chaos Mesh, you can test your system's resilience and robustness on Kubernetes by injecting various types of faults into Pods, network, file system, and even the kernel.
|
||||
|
||||
|
||||
|
||||
|
||||
## Enable App Store on KubeSphere
|
||||
|
||||
1. Make sure you have installed and enabled the [KubeSphere App Store](https://kubesphere.io/docs/pluggable-components/app-store/).
|
||||
1. Make sure you have installed and enabled the [KubeSphere App Store](../../../pluggable-components/app-store/).
|
||||
|
||||
2. You need to create a workspace, a project, and a user account (project-regular) for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the operator role. For more information, see [Create Workspaces, Projects, Users and Roles](https://kubesphere.io/docs/quick-start/create-workspace-and-project/).
|
||||
2. You need to create a workspace, a project, and a user account (project-regular) for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the operator role. For more information, see [Create Workspaces, Projects, Users and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Chaos experiments with Chaos Mesh
|
||||
|
||||
|
|
@ -22,34 +22,34 @@ linkTitle: "Deploy Chaos Mesh on KubeSphere"
|
|||
|
||||
1. Login KubeSphere as `project-regular`, search for **chaos-mesh** in the **App Store**, and click on the search result to enter the app.
|
||||
|
||||
|
||||
|
||||
|
||||
2. In the **App Information** page, click **Install** on the upper right corner.
|
||||
|
||||
|
||||
|
||||
|
||||
3. In the **App Settings** page, set the application **Name,** **Location** (as your Namespace), and **App Version**, and then click **Next** on the upper right corner.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Configure the `values.yaml` file as needed, or click **Install** to use the default configuration.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Wait for the deployment to be finished. Upon completion, Chaos Mesh will be shown as **Running** in KubeSphere.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 2: Visit Chaos Dashboard
|
||||
|
||||
1. In the **Resource Status** page, copy the **NodePort **of `chaos-dashboard`.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Access the Chaos Dashboard by entering `${NodeIP}:${NODEPORT}` in your browser. Refer to [Manage User Permissions](https://chaos-mesh.org/docs/manage-user-permissions/) to generate a Token and log into Chaos Dashboard.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 3: Create a chaos experiment
|
||||
|
||||
|
|
@ -63,20 +63,20 @@ curl -sSL https://mirrors.chaos-mesh.org/latest/web-show/deploy.sh | bash
|
|||
|
||||
1. From your web browser, visit ${NodeIP}:8081 to access the **Web Show** application.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Log in to Chaos Dashboard to create a chaos experiment. To observe the effect of network latency on the application, we set the **Target **as "Network Attack" to simulate a network delay scenario.
|
||||
|
||||
|
||||
|
||||
|
||||
The **Scope** of the experiment is set to `app: web-show`.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Start the chaos experiment by submitting it.
|
||||
|
||||
|
||||
|
||||
|
||||
Now, you should be able to visit **Web Show** to observe experiment results:
|
||||
|
||||
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ This tutorial walks you through an example of deploying etcd from the App Store
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/).
|
||||
- Please make sure you [enable the OpenPitrix system](../../../pluggable-components/app-store/).
|
||||
- You need to create a workspace, a project, and a user account (`project-regular`) for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the `operator` role. In this tutorial, you log in as `project-regular` and work in the project `demo-project` in the workspace `demo-workspace`. For more information, see [Create Workspaces, Projects, Users and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
@ -48,7 +48,7 @@ This tutorial walks you through an example of deploying [Harbor](https://goharbo
|
|||
|
||||
1. Based on the field `expose.type` you set in the configuration file, the access method may be different. As this example uses `nodePort` to access Harbor, visit `http://<NodeIP>:30002` as set in the previous step.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -58,7 +58,7 @@ This tutorial walks you through an example of deploying [Harbor](https://goharbo
|
|||
|
||||
2. Log in to Harbor using the default account and password (`admin/Harbor12345`). The password is defined in the field `harborAdminPassword` in the configuration file.
|
||||
|
||||
|
||||
|
||||
|
||||
## FAQ
|
||||
|
||||
|
|
@ -11,7 +11,7 @@ This tutorial walks you through an example of deploying Memcached from the App S
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/).
|
||||
- Please make sure you [enable the OpenPitrix system](../../../pluggable-components/app-store/).
|
||||
- You need to create a workspace, a project, and a user account (`project-regular`) for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the `operator` role. In this tutorial, you log in as `project-regular` and work in the project `demo-project` in the workspace `demo-workspace`. For more information, see [Create Workspaces, Projects, Users and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
@ -44,9 +44,9 @@ To access MinIO outside the cluster, you need to expose the app through a NodePo
|
|||
|
||||
6. Access the MinIO browser through `<NodeIP>:<NodePort>` using `accessKey` and `secretKey`.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -43,7 +43,7 @@ This tutorial walks you through an example of deploying MongoDB from the App Sto
|
|||
|
||||
3. In the pop-up window, enter commands in the terminal directly to use the app.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -12,7 +12,7 @@ This tutorial walks you through an example of deploying MySQL from the App Store
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/).
|
||||
- Please make sure you [enable the OpenPitrix system](../../../pluggable-components/app-store/).
|
||||
- You need to create a workspace, a project, and a user account for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the `operator` role. In this tutorial, you log in as `project-regular` and work in the project `demo-project` in the workspace `demo-workspace`. For more information, see [Create Workspaces, Projects, Users and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
@ -37,7 +37,7 @@ This tutorial walks you through an example of deploying MySQL from the App Store
|
|||
|
||||
3. In the terminal, execute `mysql -uroot -ptesting` to log in to MySQL as the root user.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 3: Access the MySQL database outside the cluster
|
||||
|
||||
|
|
@ -53,9 +53,9 @@ To access MySQL outside the cluster, you need to expose the app through a NodePo
|
|||
|
||||
5. To access your MySQL database, you need to use the MySQL client or install a third-party application such as SQLPro Studio for the connection. The following example demonstrates how to access the MySQL database through SQLPro Studio.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ To access NGINX outside the cluster, you need to expose the app through a NodePo
|
|||
|
||||
5. Access NGINX through `<NodeIP>:<NodePort>`.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ To access PostgreSQL outside the cluster, you need to expose the app through a N
|
|||
|
||||
5. Expand the Pod menu under **Pods** and click the **Terminal** icon. In the pop-up window, enter commands directly to access the database.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -11,7 +11,7 @@ This tutorial walks you through an example of how to deploy RabbitMQ from the Ap
|
|||
|
||||
## Prerequisites
|
||||
|
||||
- Please make sure you [enable the OpenPitrix system](https://kubesphere.io/docs/pluggable-components/app-store/).
|
||||
- Please make sure you [enable the OpenPitrix system](../../../pluggable-components/app-store/).
|
||||
- You need to create a workspace, a project, and a user account for this tutorial. The account needs to be a platform regular user and to be invited as the project operator with the `operator` role. In this tutorial, you log in as `project-regular` and work in the project `demo-project` in the workspace `demo-workspace`. For more information, see [Create Workspaces, Projects, Users and Roles](../../../quick-start/create-workspace-and-project/).
|
||||
|
||||
## Hands-on Lab
|
||||
|
|
@ -48,9 +48,9 @@ To access RabbitMQ outside the cluster, you need to expose the app through a Nod
|
|||
|
||||
5. Access RabbitMQ **management** through `<NodeIP>:<NodePort>`. Note that the username and password are those you set in **Step 1**.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -45,6 +45,6 @@ We recommend you to use the latest version of RadonDB MySQL. For deployment inst
|
|||
|
||||
3. In the pop-up window, enter commands in the terminal directly to use the app.
|
||||
|
||||
|
||||
|
||||
|
||||
4. If you want to access RadonDB MySQL outside the cluster, see [the open-source project of RadonDB MySQL](https://github.com/radondb/radondb-mysql-kubernetes) in detail.
|
||||
|
|
@ -57,6 +57,6 @@ This tutorial demonstrates how to deploy RadonDB PostgreSQL from the App Store o
|
|||
psql -h <Pod name> -p 5432 -U postgres -d postgres
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
4. If you want to access RadonDB PostgreSQL outside the cluster, see [the open-source project of RadonDB PostgreSQL](https://github.com/radondb/radondb-postgresql-kubernetes) in detail.
|
||||
|
|
@ -43,6 +43,6 @@ This tutorial walks you through an example of deploying Redis from the App Store
|
|||
|
||||
3. In the pop-up window, use the `redis-cli` command in the terminal to use the app.
|
||||
|
||||
|
||||
|
||||
|
||||
4. For more information, see [the official documentation of Redis](https://redis.io/documentation).
|
||||
|
|
@ -36,7 +36,7 @@ This tutorial walks you through an example of deploying Tomcat from the App Stor
|
|||
|
||||
3. You can view deployed projects in `/usr/local/tomcat/webapps`.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 3: Access a Tomcat project from your browser
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ To access a Tomcat project outside the cluster, you need to expose the app throu
|
|||
|
||||
5. Access the sample Tomcat project through `<NodeIP>:<NodePort>/sample` in your browser.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -121,7 +121,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
|
|||
$ kubectl edit chi clickho-749j8s -n demo-project
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
|
|||
$ kubectl exec -it chi-clickho-749j8s-all-nodes-0-0-0 -n demo-project -- clickhouse-client --user=clickhouse --password=c1ickh0use0perator
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ This tutorial demonstrates how to deploy GitLab on KubeSphere.
|
|||
|
||||
1. Go to **Secrets** under **Configuration**, enter `gitlab-initial-root-password` in the search box, and then press **Enter** on your keyboard to search the Secret.
|
||||
|
||||
2. Click the Secret to go to its detail page, and then click <img src="/images/docs/appstore/external-apps/deploy-gitlab/eye-icon.png" width="20px" alt="icon" /> in the upper-right corner to view the password. Make sure you copy it.
|
||||
2. Click the Secret to go to its detail page, and then click <img src="/images/docs/v3.3/appstore/external-apps/deploy-gitlab/eye-icon.png" width="20px" /> in the upper-right corner to view the password. Make sure you copy it.
|
||||
|
||||
### Step 4: Edit the hosts file
|
||||
|
||||
|
|
@ -108,9 +108,9 @@ This tutorial demonstrates how to deploy GitLab on KubeSphere.
|
|||
|
||||
2. Access GitLab through `http://gitlab.demo-project.svc.cluster.local:31246` using the root account and its initial password (`root/ojPWrWECLWN0XFJkGs7aAqtitGMJlVfS0fLEDE03P9S0ji34XDoWmxs2MzgZRRWF`).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -24,7 +24,7 @@ This tutorial demonstrates how to deploy Litmus on KubeSphere and create chaos e
|
|||
### Step 1: Add an app repository
|
||||
1. In your workspace, go to **App Repositories** under **App Management**, and then click **Add**.
|
||||
|
||||
2. In the dialog that appears, set a name for the repository (for example, `litmus`) and enter the URL `https://litmuschaos.github.io/litmus-helm/`. Click **Validate** to verify the URL. You will see <img src="/images/docs/zh-cn/appstore/external-apps/deploy-litmus/checkmark.png" width="20" /> icon if the URL is available. Click **OK** to continue.
|
||||
2. In the dialog that appears, set a name for the repository (for example, `litmus`) and enter the URL `https://litmuschaos.github.io/litmus-helm/`. Click **Validate** to verify the URL. You will see <img src="/images/docs/v3.3/zh-cn/appstore/external-apps/deploy-litmus/checkmark.png" width="20" /> icon if the URL is available. Click **OK** to continue.
|
||||
|
||||
3. The app repository displays in the list after it is successfully imported.
|
||||
|
||||
|
|
@ -59,9 +59,9 @@ This tutorial demonstrates how to deploy Litmus on KubeSphere and create chaos e
|
|||
|
||||
2. You can access Litmus `Portal` through `${NodeIP}:${NODEPORT}` using the default username and password (`admin`/`litmus`).
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
You may need to open the port in your security groups and configure port forwarding rules depending on where your Kubernetes cluster is deployed. Make sure you use your own `NodeIP`.
|
||||
|
|
@ -107,7 +107,7 @@ For details about how to deploy External Agent, see [Litmus Docs](https://litmus
|
|||
|
||||
On the Litmus `Portal`, you can see that the experiment is successful.
|
||||
|
||||
|
||||
|
||||
|
||||
You can click a specific workflow node to view its detailed logs.
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ For details about how to deploy External Agent, see [Litmus Docs](https://litmus
|
|||
|
||||
You can ping the Pod IP address to test the packet loss rate.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ This tutorial demonstrates how to deploy MeterSphere on KubeSphere.
|
|||
|
||||
2. You can access MeterSphere through `<NodeIP>:<NodePort>` using the default account and password (`admin/metersphere`).
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ This tutorial demonstrates how to deploy RadonDB MySQL Operator and a RadonDB My
|
|||
|
||||
Your repository displays in the list after it is successfully imported to KubeSphere.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 2: Deploy RadonDB MySQL Operator
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ This tutorial demonstrates how to deploy RadonDB MySQL Operator and a RadonDB My
|
|||
On the **Chart Files** tab, you can view the configuration and edit the `.yaml` files.
|
||||
On the **Version** list, you can view the app versions and select a version.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Click **Deploy**, go to the **Basic Information** page.
|
||||
|
||||
|
|
@ -139,7 +139,7 @@ Go to the `demo-project` project management page, access RadonDB MySQL through t
|
|||
|
||||
4. In terminal window, run the following command to access the RadonDB MySQL cluster.
|
||||
|
||||
|
||||
|
||||
|
||||
**Method 2**
|
||||
|
||||
|
|
@ -157,4 +157,4 @@ In the blow command, `sample-mysql-0` is the Pod name and `demo-project` is the
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
|
@ -132,7 +132,7 @@ The process of deploying a TiDB cluster is similar to deploying TiDB Operator.
|
|||
|
||||
2. TiDB integrates Prometheus and Grafana to monitor performance of the database cluster. For example, you can access Grafana through `<NodeIP>:<NodePort>` to view metrics.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -7,7 +7,7 @@ linkTitle: "Cluster Administration"
|
|||
|
||||
weight: 8000
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
icon: "/images/docs/v3.3/docs.svg"
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -61,14 +61,14 @@ You need to prepare a user with the `platform-admin` role, for example, `admin`.
|
|||
3. Click the **Monitoring** tab to view the monitoring metrics of the cluster gateway.
|
||||
4. Click the **Configuration Options** tab to view configuration options of the cluster gateway.
|
||||
5. Click the **Gateway Logs** tab to view logs of the cluster gateway.
|
||||
6. Click the **Resource Status** tab to view workload status of the cluster gateway. Click <img src="/images/docs/common-icons/replica-plus-icon.png" alt="icon" width="15" /> or <img src="/images/docs/common-icons/replica-minus-icon.png" alt="icon" width="15" /> to scale up or scale down the number of replicas.
|
||||
6. Click the **Resource Status** tab to view workload status of the cluster gateway. Click <img src="/images/docs/v3.3/common-icons/replica-plus-icon.png" width="15" /> or <img src="/images/docs/v3.3/common-icons/replica-minus-icon.png" width="15" /> to scale up or scale down the number of replicas.
|
||||
7. Click the **Metadata** tab to view annotations of the cluster gateway.
|
||||
|
||||
## View Project Gateways
|
||||
|
||||
On the **Gateway Settings** page, click the **Project Gateway** tab to view project gateways.
|
||||
|
||||
Click <img src="/images/docs/project-administration/role-and-member-management/three-dots.png" width="20px"> on the right of a project gateway to select an operation from the drop-down menu:
|
||||
Click <img src="/images/docs/v3.3/project-administration/role-and-member-management/three-dots.png" width="20px"> on the right of a project gateway to select an operation from the drop-down menu:
|
||||
|
||||
- **Edit**: Edit configurations of the project gateway.
|
||||
- **Disable**: Disable the project gateway.
|
||||
|
|
@ -48,7 +48,7 @@ KubeSphere also has built-in policies which will trigger alerts if conditions de
|
|||
|
||||
## Edit an Alerting Policy
|
||||
|
||||
To edit an alerting policy after it is created, on the **Alerting Policies** page, click <img src="/images/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policies-node-level/edit-policy.png" height="25px"> on the right of the alerting policy.
|
||||
To edit an alerting policy after it is created, on the **Alerting Policies** page, click <img src="/images/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policies-node-level/edit-policy.png" height="25px"> on the right of the alerting policy.
|
||||
|
||||
1. Click **Edit** from the drop-down list and edit the alerting policy following the same steps as you create it. Click **OK** on the **Message Settings** page to save it.
|
||||
|
||||
|
|
@ -62,8 +62,8 @@ Under **Monitoring**, the **Alert Monitoring** chart shows the actual usage or a
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can click <img src="/images/docs/cluster-administration/cluster-wide-alerting-and-notification/alerting-policies-node-level/drop-down-list.png" width='20' /> in the upper-right corner to select or custom a time range for the alert monitoring chart.
|
||||
You can click <img src="/images/docs/v3.3/cluster-administration/cluster-wide-alerting-and-notification/alerting-policies-node-level/drop-down-list.png" width='20' /> in the upper-right corner to select or custom a time range for the alert monitoring chart.
|
||||
|
||||
You can also click <img src="/images/docs/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/refresh.png" width='25' /> in the upper-right corner to manually refresh the alert monitoring chart.
|
||||
You can also click <img src="/images/docs/v3.3/zh-cn/cluster-administration/cluster-wide-alerting-and-notification/alerting-policy-node-level/refresh.png" width='25' /> in the upper-right corner to manually refresh the alert monitoring chart.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -10,7 +10,7 @@ Alertmanager handles alerts sent by client applications such as the Prometheus s
|
|||
|
||||
KubeSphere has been using Prometheus as its monitoring service's backend from the first release. Starting from v3.0, KubeSphere adds Alertmanager to its monitoring stack to manage alerts sent from Prometheus as well as other components such as [kube-events](https://github.com/kubesphere/kube-events) and kube-auditing.
|
||||
|
||||
|
||||
|
||||
|
||||
## Use Alertmanager to Manage Prometheus Alerts
|
||||
|
||||
|
|
@ -41,9 +41,9 @@ Cluster nodes are only accessible to cluster administrators. Some node metrics a
|
|||
## Node Management
|
||||
On the **Cluster Nodes** page, you can perform the following operations:
|
||||
|
||||
- **Cordon/Uncordon**: Click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right of the cluster node, and then click **Cordon** or **Uncordon**. Marking a node as unschedulable is very useful during a node reboot or other maintenance. The Kubernetes scheduler will not schedule new Pods to this node if it's been marked unschedulable. Besides, this does not affect existing workloads already on the node.
|
||||
- **Cordon/Uncordon**: Click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right of the cluster node, and then click **Cordon** or **Uncordon**. Marking a node as unschedulable is very useful during a node reboot or other maintenance. The Kubernetes scheduler will not schedule new Pods to this node if it's been marked unschedulable. Besides, this does not affect existing workloads already on the node.
|
||||
|
||||
- **Open Terminal**：Click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right of the cluster node, and then click **Open Terminal**. This makes it convenient for you to manage nodes, such as modifying node configurations and downloading images.
|
||||
- **Open Terminal**：Click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right of the cluster node, and then click **Open Terminal**. This makes it convenient for you to manage nodes, such as modifying node configurations and downloading images.
|
||||
|
||||
- **Edit Taints**：Taints allow a node to repel a set of pods. To edit a taint, select the check box before the target node. On the **Edit Taints** that is displayed, you can add, delete, or modify taints.
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ This tutorial demonstrates how to configure a email server and add recipients to
|
|||
|
||||
2. After it is added, the email address of a recipient will be listed under **Recipient Settings**. You can add up to 50 recipients and all of them will be able to receive email notifications.
|
||||
|
||||
3. To remove a recipient, hover over the email address you want to remove, then click <img src="/images/docs/common-icons/trashcan.png" width="25" height="25" />.
|
||||
3. To remove a recipient, hover over the email address you want to remove, then click <img src="/images/docs/v3.3/common-icons/trashcan.png" width="25" height="25" />.
|
||||
|
||||
### Set notification conditions
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ This tutorial demonstrates how to configure a email server and add recipients to
|
|||
|
||||
2. You can click **Add** to add notification conditions.
|
||||
|
||||
3. You can click <img src="/images/docs/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
3. You can click <img src="/images/docs/v3.3/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
|
||||
4. After the configurations are complete, you can click **Send Test Message** for verification.
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ You must provide the Slack token on the console for authentication so that KubeS
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
9. You can click **Add** to add notification conditions, or click <img src="/images/docs/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
9. You can click **Add** to add notification conditions, or click <img src="/images/docs/v3.3/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
|
||||
10. After the configurations are complete, you can click **Send Test Message** for verification.
|
||||
|
||||
|
|
@ -47,7 +47,7 @@ You need to prepare a user granted the `platform-admin` role. For more informati
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
6. You can click **Add** to add notification conditions, or click <img src="/images/docs/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
6. You can click **Add** to add notification conditions, or click <img src="/images/docs/v3.3/common-icons/trashcan.png" width='25' height='25' /> on the right of a notification condition to delete the condition.
|
||||
|
||||
7. After the configurations are complete, you can click **Send Test Message** for verification.
|
||||
|
||||
|
|
@ -16,7 +16,7 @@ You need to have a user with the `platform-admin` role, for example, the `admin`
|
|||
|
||||
1. Log in to the KubeSphere console as `admin`.
|
||||
|
||||
2. Click <img src="/images/docs/common-icons/hammer.png" width="15" /> in the lower-right corner and select **Kubectl**.
|
||||
2. Click <img src="/images/docs/v3.3/common-icons/hammer.png" width="15" /> in the lower-right corner and select **Kubectl**.
|
||||
|
||||
3. In the displayed dialog box, run the following command:
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ layout: "single"
|
|||
linkTitle: "Cluster Shutdown and Restart"
|
||||
weight: 8800
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
icon: "/images/docs/v3.3/docs.svg"
|
||||
---
|
||||
This document describes the process of gracefully shutting down your Kubernetes cluster and how to restart it. You might need to temporarily shut down your cluster for maintenance reasons.
|
||||
|
||||
|
|
@ -6,7 +6,7 @@ layout: "second"
|
|||
linkTitle: "DevOps User Guide"
|
||||
weight: 11000
|
||||
|
||||
icon: "/images/docs/docs.svg"
|
||||
icon: "/images/docs/v3.3/docs.svg"
|
||||
---
|
||||
|
||||
To deploy and manage your CI/CD tasks and related workloads on your Kubernetes clusters, you use the KubeSphere DevOps system. This chapter demonstrates how to manage and work in DevOps projects, including running pipelines, creating credentials, and integrating tools.
|
||||
|
|
@ -16,7 +16,7 @@ weight: 11430
|
|||
|
||||
As is shown in the graph below, there is the workflow for a Maven project in KubeSphere DevOps, which uses a Jenkins pipeline to build and deploy the Maven project. All steps are defined in the pipeline.
|
||||
|
||||
|
||||
|
||||
|
||||
At first, the Jenkins Master creates a Pod to run the pipeline. Kubernetes creates the Pod as the agent of Jenkins Master, and the Pod will be destroyed after the pipeline finished. The main process includes cloning code, building and pushing an image, and deploying the workload.
|
||||
|
||||
|
|
@ -22,7 +22,7 @@ This tutorial demonstrates how to create a multi-cluster pipeline on KubeSphere.
|
|||
|
||||
This tutorial uses three clusters to serve as three isolated environments in the workflow. See the diagram as below.
|
||||
|
||||
|
||||
|
||||
|
||||
The three clusters are used for development, testing, and production respectively. Once codes get submitted to a Git repository, a pipeline will be triggered to run through the following stages—`Unit Test`, `SonarQube Analysis`, `Build & Push`, and `Deploy to Development Cluster`. Developers use the development cluster for self-testing and validation. When developers give approval, the pipeline will proceed to the stage of `Deploy to Testing Cluster` for stricter validation. Finally, the pipeline, with necessary approval ready, will reach the stage of `Deploy to Production Cluster` to provide services externally.
|
||||
|
||||
|
|
@ -21,7 +21,7 @@ This tutorial demonstrates how to use Nexus in pipelines on KubeSphere.
|
|||
|
||||
### Step 1: Get a Repository URL on Nexus
|
||||
|
||||
1. Log in to the Nexus console as `admin` and click <img src="/images/docs/devops-user-guide/examples/use-nexus-in-pipeline/gear.png" height="18px" /> on the top navigation bar.
|
||||
1. Log in to the Nexus console as `admin` and click <img src="/images/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipeline/gear.png" height="18px" /> on the top navigation bar.
|
||||
|
||||
2. Go to the **Repositories** page and you can see that Nexus provides three types of repository.
|
||||
|
||||
|
|
@ -37,9 +37,9 @@ This tutorial demonstrates how to use Nexus in pipelines on KubeSphere.
|
|||
|
||||
2. In your own GitHub repository of **learn-pipeline-java**, click the file `pom.xml` in the root directory.
|
||||
|
||||
3. Click <img src="/images/docs/devops-user-guide/examples/use-nexus-in-pipeline/github-edit-icon.png" height="18px" alt="icon" /> to modify the code segment of `<distributionManagement>` in the file. Set the `<id>` and use the URLs of your own Nexus repositories.
|
||||
3. Click <img src="/images/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipeline/github-edit-icon.png" height="18px" /> to modify the code segment of `<distributionManagement>` in the file. Set the `<id>` and use the URLs of your own Nexus repositories.
|
||||
|
||||
|
||||
|
||||
|
||||
4. When you finish, click **Commit changes** at the bottom of the page.
|
||||
|
||||
|
|
@ -63,7 +63,7 @@ This tutorial demonstrates how to use Nexus in pipelines on KubeSphere.
|
|||
</servers>
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ This tutorial demonstrates how to use Nexus in pipelines on KubeSphere.
|
|||
</mirrors>
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -160,11 +160,11 @@ This tutorial demonstrates how to use Nexus in pipelines on KubeSphere.
|
|||
|
||||
4. Log in to Nexus and click **Browse**. Click **maven-public** and you can see all the dependencies have been downloaded.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Go back to the **Browse** page and click **maven-snapshots**. You can see the JAR package has been uploaded to the repository.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
3. You will get this prompt:
|
||||
|
||||
|
||||
|
||||
|
||||
## Get the SonarQube Console Address
|
||||
|
||||
|
|
@ -99,15 +99,15 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
1. Click the letter **A** and select **My Account** from the menu to go to the **Profile** page.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click **Security** and enter a token name, such as `kubesphere`.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Generate** and copy the token.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice warning >}}
|
||||
|
||||
|
|
@ -133,15 +133,15 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
3. Click **Administration**, **Configuration** and **Webhooks** in turn to create a webhook.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Click **Create**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Enter **Name** and **Jenkins Console URL** (for example, the SonarQube Webhook address) in the displayed dialog box. Click **Create** to finish.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 4: Add the SonarQube configuration to ks-installer
|
||||
|
||||
|
|
@ -201,9 +201,9 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
7. Enter **Name** and **Server URL** (`http://<Node IP>:<NodePort>`). Click **Add**, select **Jenkins**, and then create the credentials with the SonarQube admin token in the displayed dialog box as shown in the second image below. After adding the credentials, select it from the drop-down list for **Server authentication token** and then click **Apply** to finish.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -250,23 +250,23 @@ You need a SonarQube token so that your pipeline can communicate with SonarQube
|
|||
|
||||
1. On the SonarQube console, click **Create new project**.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Enter a project key, such as `java-demo`, and click **Set Up**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Enter a project name, such as `java-sample`, and click **Generate**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. After the token is created, click **Continue**.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Choose **Java** and **Maven** respectively. Copy the serial number within the green box in the image below, which needs to be added in the [Credentials](../../../devops-user-guide/how-to-use/devops-settings/credential-management/#create-credentials) section if it is to be used in pipelines.
|
||||
|
||||
|
||||
|
||||
|
||||
## View Results on the KubeSphere Console
|
||||
|
||||
|
|
@ -90,7 +90,7 @@ In KubeSphere 3.3.0, you can import a GitHub, GitLab, Bitbucket, or Git-based re
|
|||
{{</ notice >}}
|
||||
|
||||
7. In the GitHub repositories that are displayed, select a repository, and click **OK**.
|
||||
8. Click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right of the imported code repository, and you can perform the following operations:
|
||||
8. Click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right of the imported code repository, and you can perform the following operations:
|
||||
|
||||
- **Edit**: Edits the alias and description of the code repository and reselects a code repository.
|
||||
- **Edit YAML**: Edits the YAML file of the code repository.
|
||||
|
|
@ -108,7 +108,7 @@ This section walks you through the process of deploying an application using a c
|
|||
</tbody>
|
||||
</table>
|
||||
|
||||
10. Click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right of the continuous deployment, and you can perform the following:
|
||||
10. Click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right of the continuous deployment, and you can perform the following:
|
||||
- **Edit Information**: Edits the alias and description.
|
||||
- **Edit YAML**: Edits the YAML file.
|
||||
- **Sync**: Triggers resources synchronization.
|
||||
|
|
@ -127,7 +127,7 @@ This section walks you through the process of deploying an application using a c
|
|||
|
||||
1. Go to the project where the continuous deployment resides, in the navigation pane on the left, click **Services**.
|
||||
|
||||
2. On the **Services** page on the left, click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right of the deployed application, and click **Edit External Access**.
|
||||
2. On the **Services** page on the left, click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right of the deployed application, and click **Edit External Access**.
|
||||
|
||||
3. In **Access Mode**, select **NodePort**, and click **OK**.
|
||||
|
||||
|
|
@ -49,7 +49,7 @@ In **DevOps Project Roles**, there are three available built-in roles as shown b
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
4. Newly created roles will be listed in **DevOps Project Roles**. You can click <img src="/images/docs/common-icons/three-dots.png" height="15px"> on the right to edit it.
|
||||
4. Newly created roles will be listed in **DevOps Project Roles**. You can click <img src="/images/docs/v3.3/common-icons/three-dots.png" height="15px"> on the right to edit it.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -61,7 +61,7 @@ In **DevOps Project Roles**, there are three available built-in roles as shown b
|
|||
|
||||
1. In **DevOps Project Settings**, select **DevOps Project Members** and click **Invite**.
|
||||
|
||||
2. Click <img src="/images/docs/common-icons/invite-member-button.png" height="15px"> to invite a user to the DevOps project. Grant the role of `pipeline-creator` to the account.
|
||||
2. Click <img src="/images/docs/v3.3/common-icons/invite-member-button.png" height="15px"> to invite a user to the DevOps project. Grant the role of `pipeline-creator` to the account.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -50,7 +50,7 @@ In the current version, there are 4 types of built-in podTemplates, i.e. `base`,
|
|||
|
||||
You can use the built-in podTemplate by specifying the label for an agent. For example, to use the nodejs podTemplate, you can set the label to `nodejs` when creating the Pipeline, as shown in the example below.
|
||||
|
||||
|
||||
|
||||
|
||||
```groovy
|
||||
pipeline {
|
||||
|
|
@ -115,11 +115,11 @@ Pipelines include [declarative pipelines](https://www.jenkins.io/doc/book/pipeli
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
2. To add a stage, click the plus icon on the left. Click the box above the **Add Step** area and set a name (for example, `Checkout SCM`) for the stage in the field **Name** on the right.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Add Step**. Select **git** from the list as the example code is pulled from GitHub. In the displayed dialog box, fill in the required field. Click **OK** to finish.
|
||||
|
||||
|
|
@ -127,21 +127,21 @@ Pipelines include [declarative pipelines](https://www.jenkins.io/doc/book/pipeli
|
|||
- **Name**. You do not need to enter the Credential ID for this tutorial.
|
||||
- **Branch**. It defaults to the master branch if you leave it blank. Enter `sonarqube` or leave it blank if you do not need the code analysis stage.
|
||||
|
||||
|
||||
|
||||
|
||||
4. The first stage is now set.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Stage 2: Unit test
|
||||
|
||||
1. Click the plus icon on the right of stage 1 to add a new stage to perform a unit test in the container. Name it `Unit Test`.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click **Add Step** and select **container** from the list. Name it `maven` and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Add Nesting Steps** to add a nested step under the `maven` container. Select **shell** from the list and enter the following command in the command line. Click **OK** to save it.
|
||||
|
||||
|
|
@ -162,27 +162,27 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
1. Click the plus icon on the right of the `Unit Test` stage to add a stage for SonarQube code analysis in the container. Name it `Code Analysis`.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click **Add Step** under **Task** in **Code Analysis** and select **container**. Name it `maven` and click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Add Nesting Steps** under the `maven` container to add a nested step. Click **withCredentials** and select the SonarQube token (`sonar-token`) from the **Name** list. Enter `SONAR_TOKEN` for **Text Variable**, then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Under the **withCredentials** step, click **Add Nesting Steps** to add a nested step for it.
|
||||
|
||||
|
||||
|
||||
|
||||
5. Click **withSonarQubeEnv**. In the displayed dialog box, do not change the default name `sonar` and click **OK** to save it.
|
||||
|
||||
|
||||
|
||||
|
||||
6. Under the **withSonarQubeEnv** step, click **Add Nesting Steps** to add a nested step for it.
|
||||
|
||||
|
||||
|
||||
|
||||
7. Click **shell** and enter the following command in the command line for the sonarqube branch and authentication. Click **OK** to finish.
|
||||
|
||||
|
|
@ -190,29 +190,29 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
mvn sonar:sonar -Dsonar.login=$SONAR_TOKEN
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
8. Click **Add Nesting Steps** (the third one) for the **container** step directly and select **timeout**. Enter `1` for time and select **Hours** for unit. Click **OK** to finish.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
9. Click **Add Nesting Steps** for the **timeout** step and select **waitForQualityGate**. Select **Start the follow-up task after the inspection** in the displayed dialog box. Click **OK** to save it.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
#### Stage 4: Build and push the image
|
||||
|
||||
1. Click the plus icon on the right of the previous stage to add a new stage to build and push images to Docker Hub. Name it `Build and Push`.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click **Add Step** under **Task** and select **container**. Name it `maven`, and then click **OK**.
|
||||
|
||||
|
||||
|
||||
|
||||
3. Click **Add Nesting Steps** under the `maven` container to add a nested step. Select **shell** from the list, and enter the following command in the displayed dialog box. Click **OK** to finish.
|
||||
|
||||
|
|
@ -220,7 +220,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
mvn -Dmaven.test.skip=true clean package
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
4. Click **Add Nesting Steps** again and select **shell**. Enter the following command in the command line to build a Docker image based on the [Dockerfile](https://github.com/kubesphere/devops-maven-sample/blob/sonarqube/Dockerfile-online). Click **OK** to confirm.
|
||||
|
||||
|
|
@ -234,7 +234,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
docker build -f Dockerfile-online -t $REGISTRY/$DOCKERHUB_NAMESPACE/$APP_NAME:SNAPSHOT-$BUILD_NUMBER .
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
5. Click **Add Nesting Steps** again and select **withCredentials**. Fill in the following fields in the displayed dialog box. Click **OK** to confirm.
|
||||
|
||||
|
|
@ -248,7 +248,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
6. Click **Add Nesting Steps** (the first one) in the **withCredentials** step created above. Select **shell** and enter the following command in the displayed dialog box, which is used to log in to Docker Hub. Click **OK** to confirm.
|
||||
|
||||
|
|
@ -256,7 +256,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
echo "$DOCKER_PASSWORD" | docker login $REGISTRY -u "$DOCKER_USERNAME" --password-stdin
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
7. Click **Add nesting steps** in the **withCredentials** step. Select **shell** and enter the following command to push the SNAPSHOT image to Docker Hub. Click **OK** to finish.
|
||||
|
||||
|
|
@ -264,27 +264,27 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
docker push $REGISTRY/$DOCKERHUB_NAMESPACE/$APP_NAME:SNAPSHOT-$BUILD_NUMBER
|
||||
```
|
||||
|
||||
|
||||
|
||||
|
||||
#### Stage 5: Generate the artifact
|
||||
|
||||
1. Click the plus icon on the right of the **Build and Push** stage to add a new stage to save artifacts and name it `Artifacts`. This example uses a JAR package.
|
||||
|
||||
|
||||
|
||||
|
||||
2. With the **Artifacts** stage selected, click **Add Step** under **Task** and select **archiveArtifacts**. Enter `target/*.jar` in the displayed dialog box, which is used to set the archive path of artifacts in Jenkins. Click **OK** to finish.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Stage 6: Deploy to development
|
||||
|
||||
1. Click the plus icon on the right of the stage **Artifacts** to add the last stage. Name it `Deploy to Dev`. This stage is used to deploy resources to your development environment (namely, the project of `kubesphere-sample-dev`).
|
||||
|
||||
|
||||
|
||||
|
||||
2. Click **Add Step** under the **Deploy to Dev** stage. Select **input** from the list and enter `@project-admin` in the **Message** field, which means the account `project-admin` will review this pipeline when it runs to this stage. Click **OK** to save it.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -320,7 +320,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
On the **Pipelines** page, you can click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right side of the pipeline and then select **Copy** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of these pipelines and then click **Run** to run them in a batch.
|
||||
On the **Pipelines** page, you can click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right side of the pipeline and then select **Copy** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of these pipelines and then click **Run** to run them in a batch.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -328,13 +328,13 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
1. You need to manually run the pipeline that is created through the graphical editing panel. Click **Run**, and you can see three string parameters defined in Step 3. Click **OK** to run the pipeline.
|
||||
|
||||
|
||||
|
||||
|
||||
2. To see the status of a pipeline, go to the **Run Records** tab and click the record you want to view.
|
||||
|
||||
3. Wait for a while and the pipeline stops at the stage **Deploy to Dev** if it runs successfully. As the reviewer of the pipeline, `project-admin` needs to approve it before resources are deployed to the development environment.
|
||||
|
||||
|
||||
|
||||
|
||||
4. Log out of KubeSphere and log back in to the console as `project-admin`. Go to your DevOps project and click the pipeline `graphical-pipeline`. Under the **Run Records** tab, click the record to be reviewed. To approve the pipeline, click **Proceed**.
|
||||
|
||||
|
|
@ -350,13 +350,13 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
Click the **Artifacts** tab and then click the icon on the right to download the artifact.
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 8: View code analysis results
|
||||
|
||||
On the **Code Check** page, view the code analysis result of this example pipeline, which is provided by SonarQube. If you do not configure SonarQube in advance, this section is not available. For more information, see [Integrate SonarQube into Pipelines](../../../how-to-integrate/sonarqube/).
|
||||
|
||||
|
||||
|
||||
|
||||
### Step 9: Verify Kubernetes resources
|
||||
|
||||
|
|
@ -374,7 +374,7 @@ On the **Code Check** page, view the code analysis result of this example pipeli
|
|||
|
||||
4. Now that the pipeline has run successfully, an image will be pushed to Docker Hub. Log in to Docker Hub and check the result.
|
||||
|
||||
|
||||
|
||||
|
||||
5. The app is named `devops-sample` as it is the value of `APP_NAME` and the tag is the value of `SNAPSHOT-$BUILD_NUMBER`. `$BUILD_NUMBER` is the serial number of a record under the **Run Records** tab.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ There are eight stages as shown below in this example pipeline.
|
|||
|
||||
3. You also need to create a GitHub personal access token with the permission as shown in the below image, and then use the generated token to create Account Credentials (for example, `github-token`) for GitHub authentication in your DevOps project.
|
||||
|
||||
|
||||
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -83,7 +83,7 @@ There are eight stages as shown below in this example pipeline.
|
|||
|
||||
3. Click the edit icon on the right to edit environment variables.
|
||||
|
||||
|
||||
|
||||
|
||||
| Items | Value | Description |
|
||||
| :--- | :--- | :--- |
|
||||
|
|
@ -185,7 +185,7 @@ The account `project-admin` needs to be created in advance since it is the revie
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
- You can click <img src="/images/docs/common-icons/three-dots.png" width="15" /> on the right side of the pipeline and then select **Copy** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of these pipelines and then click **Run** to run them in a batch.
|
||||
- You can click <img src="/images/docs/v3.3/common-icons/three-dots.png" width="15" /> on the right side of the pipeline and then select **Copy** to create a copy of it. If you need to concurrently run multiple pipelines that don't contain multiple branches, you can select all of these pipelines and then click **Run** to run them in a batch.
|
||||
- The pipeline details page shows **Sync Status**. It reflects the synchronization result between KubeSphere and Jenkins, and you can see the **Successful** icon if the synchronization is successful.
|
||||
|
||||
{{</ notice >}}
|
||||
|
|
@ -20,7 +20,7 @@ The built-in Jenkins cannot share the same email configuration with the platform
|
|||
|
||||
2. If you have enabled the [multi-cluster feature](../../../../multicluster-management/) with member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
|
||||
|
||||
3. Go to **Workloads** under **Application Workloads**, and select the project **kubesphere-devops-system** from the drop-down list. Click <img src="/images/docs/common-icons/three-dots.png" height="15" /> on the right of `devops-jenkins` and select **Edit YAML** to edit its YAML.
|
||||
3. Go to **Workloads** under **Application Workloads**, and select the project **kubesphere-devops-system** from the drop-down list. Click <img src="/images/docs/v3.3/common-icons/three-dots.png" height="15" /> on the right of `devops-jenkins` and select **Edit YAML** to edit its YAML.
|
||||
|
||||
4. Scroll down to the fields in the image below which you need to specify. Click **OK** when you finish to save changes.
|
||||
|
||||
|
|
@ -30,7 +30,7 @@ The built-in Jenkins cannot share the same email configuration with the platform
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
||||
|
||||
| Environment Variable Name | Description |
|
||||
| ------------------------- | -------------------------------- |
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue