mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Hyphenate compounds across guides
Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
This commit is contained in:
Sherlock113
parent
f996b150bd
commit
28e5ccf6a6
|
|
@ -105,7 +105,7 @@ Now that you have Helm charts ready, you can upload them to KubeSphere as app te
|
|||
|
||||
You can release apps you have uploaded to KubeSphere to the public repository, also known as the App Store. In this way, all tenants on the platform can see these apps and deploy them if they have necessary permissions regardless of the workspace they belong to.
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Access Control**.
|
||||
1. Click **Platform** in the top-left corner and select **Access Control**.
|
||||
|
||||
2. On the **Workspaces** page, click the workspace where you have uploaded the Helm charts above.
|
||||
|
||||
|
|
@ -119,7 +119,7 @@ You can release apps you have uploaded to KubeSphere to the public repository, a
|
|||
|
||||
|
||||
|
||||
5. After the app is submitted for review, I need to approve it before it can be released to the App Store. Click **Platform** in the top left corner and select **App Store Management**.
|
||||
5. After the app is submitted for review, I need to approve it before it can be released to the App Store. Click **Platform** in the top-left corner and select **App Store Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -131,7 +131,7 @@ You can release apps you have uploaded to KubeSphere to the public repository, a
|
|||
|
||||
|
||||
|
||||
8. After the app is approved, you can release it to the App Store. Click **Platform** in the top left corner, select **Access Control**, and go back to your workspace. Select **App Templates** from the navigation bar and click **tidb-operator**.
|
||||
8. After the app is approved, you can release it to the App Store. Click **Platform** in the top-left corner, select **Access Control**, and go back to your workspace. Select **App Templates** from the navigation bar and click **tidb-operator**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -141,7 +141,7 @@ You can release apps you have uploaded to KubeSphere to the public repository, a
|
|||
|
||||
|
||||
|
||||
11. To view the app released, click **App Store** in the top left corner and you can see it in the App Store. Likewise, you can deploy **tidb-cluster** to the App Store by following the same step.
|
||||
11. To view the app released, click **App Store** in the top-left corner and you can see it in the App Store. Likewise, you can deploy **tidb-cluster** to the App Store by following the same step.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -40,7 +40,7 @@ Therefore, I select QingCloud Kubernetes Engine (QKE) to prepare the environment
|
|||
|
||||
|
||||
|
||||
3. Use the built-in **Web Kubectl** from the Toolkit in the bottom right corner to execute the following command to install TiDB Operator CRD:
|
||||
3. Use the built-in **Web Kubectl** from the Toolkit in the bottom-right corner to execute the following command to install TiDB Operator CRD:
|
||||
|
||||
```bash
|
||||
kubectl apply -f https://raw.githubusercontent.com/pingcap/tidb-operator/v1.1.6/manifests/crd.yaml
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ This is basically the same as what I did last time as we need to make sure all o
|
|||
|
||||
- As NFS itself does not have an internal provisioner, I will be using NFS-client Provisioner for dynamic provisioning of volumes.
|
||||
|
||||
- `kubectl` is integrated into the console of KubeSphere. You can run commands with it from **Toolbox** in the bottom right corner of the KubeSphere dashboard.
|
||||
- `kubectl` is integrated into the console of KubeSphere. You can run commands with it from **Toolbox** in the bottom-right corner of the KubeSphere dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -113,7 +113,7 @@ To mount a volume to your workload, you need to create a [PersistentVolumeClaim]
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
To create workloads in KubeSphere, you can create and apply YAML files just as what you did before (**Edit Mode** in the top right corner). At the same time, you can also set parameters for your workloads on the KubeSphere dashboard one by one. I will not talk about the whole process in detail as this article is mainly about how to configure storage and create volumes. Have a look at [the KubeSphere documentation](https://kubesphere.io/docs/project-user-guide/application-workloads/deployments/) to learn more about how to create workloads.
|
||||
To create workloads in KubeSphere, you can create and apply YAML files just as what you did before (**Edit Mode** in the top-right corner). At the same time, you can also set parameters for your workloads on the KubeSphere dashboard one by one. I will not talk about the whole process in detail as this article is mainly about how to configure storage and create volumes. Have a look at [the KubeSphere documentation](https://kubesphere.io/docs/project-user-guide/application-workloads/deployments/) to learn more about how to create workloads.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -169,7 +169,7 @@ We surely can create an application through the Web UI, but let's use the CLI to
|
|||
|
||||
|
||||
|
||||
3. Click it to see its details. You can also click the icon in the upper right corner to view its topology diagram.
|
||||
3. Click it to see its details. You can also click the icon in the upper-right corner to view its topology diagram.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -317,7 +317,7 @@ You can verify that NFS-client has been successfully installed either from the c
|
|||
|
||||
1. The `ks-console` Service is being exposed through a NodePort. Log in to the console at `<node IP>:30880` with the default account and password (`admin/P@88w0rd`). You may need to open the port in your security groups and configure relevant port forwarding rules depending on your environment.
|
||||
|
||||
2. Click **Platform** in the top left corner and go to **Cluster Management**. In **Storage Classes** under **Storage**, you can see two storage classes:
|
||||
2. Click **Platform** in the top-left corner and go to **Cluster Management**. In **Storage Classes** under **Storage**, you can see two storage classes:
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ Using [Redis](https://redis.io/) as an example application, this tutorial demons
|
|||
|
||||
You need to create two accounts first, one for ISVs (`isv`) and the other (`reviewer`) for app technical reviewers.
|
||||
|
||||
1. Log in to the KubeSphere console with the account `admin`. Click **Platform** in the top left corner and select **Access Control**. In **Account Roles**, click **Create**.
|
||||
1. Log in to the KubeSphere console with the account `admin`. Click **Platform** in the top-left corner and select **Access Control**. In **Account Roles**, click **Create**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -135,7 +135,7 @@ The version number must start with a number and contain decimal points.
|
|||
|
||||
### Step 3: Review the application
|
||||
|
||||
1. Log out of KubeSphere and log back in as `reviewer`. Click **Platform** in the top left corner and select **App Store Management**. On the **App Review** page, the app submitted in the previous step displays under the tab **Unprocessed**.
|
||||
1. Log out of KubeSphere and log back in as `reviewer`. Click **Platform** in the top-left corner and select **App Store Management**. On the **App Review** page, the app submitted in the previous step displays under the tab **Unprocessed**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -157,7 +157,7 @@ After the app is approved, `isv` can release the Redis application to the App St
|
|||
|
||||
|
||||
|
||||
3. Click **View in Store** to go to its **App Info** page in the App Store. Alternatively, click **App Store** in the top left corner and you can also see the app.
|
||||
3. Click **View in Store** to go to its **App Info** page in the App Store. Alternatively, click **App Store** in the top-left corner and you can also see the app.
|
||||
|
||||
|
||||
|
||||
|
|
@ -267,7 +267,7 @@ To follow the steps below, you must deploy an app of one of its old versions fir
|
|||
|
||||
You can choose to remove an app entirely from the App Store or suspend a specific app version.
|
||||
|
||||
1. Log in to KubeSphere as `reviewer`. Click **Platform** in the top left corner and go to **App Store Management**. On the **App Store** page, click Redis.
|
||||
1. Log in to KubeSphere as `reviewer`. Click **Platform** in the top-left corner and go to **App Store Management**. On the **App Store** page, click Redis.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of deploying etcd from the App Store
|
|||
|
||||
### Step 1: Deploy etcd from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ This tutorial walks you through an example of deploying [Harbor](https://goharbo
|
|||
|
||||
### Step 1: Deploy Harbor from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ This tutorial walks you through an example of deploying Memcached from the App S
|
|||
|
||||
### Step 1: Deploy Memcached from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ This tutorial walks you through an example of deploying MinIO from the App Store
|
|||
|
||||
### Step 1: Deploy MinIO from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of deploying MongoDB from the App Sto
|
|||
|
||||
### Step 1: Deploy MongoDB from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of deploying MySQL from the App Store
|
|||
|
||||
### Step 1: Deploy MySQL from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of deploying NGINX from the App Store
|
|||
|
||||
### Step 1: Deploy NGINX from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of how to deploy PostgreSQL from the
|
|||
|
||||
### Step 1: Deploy PostgreSQL from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ This tutorial walks you through an example of how to deploy RabbitMQ from the Ap
|
|||
|
||||
### Step 1: Deploy RabbitMQ from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial demonstrates how to deploy RadonDB MySQL from the App Store of Kub
|
|||
|
||||
### Step 1: Deploy RadonDB MySQL from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
2. Find RadonDB MySQL and click **Deploy** on the **App Information** page.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial walks you through an example of deploying Redis from the App Store
|
|||
|
||||
### Step 1: Deploy Redis from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ This tutorial walks you through an example of deploying Tomcat from the App Stor
|
|||
|
||||
### Step 1: Deploy Tomcat from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
|
|||
|
||||
### Step 1: Deploy ClickHouse Operator
|
||||
|
||||
1. Log in to the KubeSphere Web console as `admin`, and use **Kubectl** from the **Toolbox** in the bottom right corner to run the following command to install ClickHouse Operator. It is recommended that you have at least two worker nodes available in your cluster.
|
||||
1. Log in to the KubeSphere Web console as `admin`, and use **Kubectl** from the **Toolbox** in the bottom-right corner to run the following command to install ClickHouse Operator. It is recommended that you have at least two worker nodes available in your cluster.
|
||||
|
||||
```bash
|
||||
kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/master/clickhouse-operator-install.yml
|
||||
|
|
@ -142,7 +142,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
|
|||
|
||||
### Step 5: Access the ClickHouse Cluster
|
||||
|
||||
1. Log out of KubeSphere and log back in as `admin`. Hover your cursor over the hammer icon in the bottom right corner and then select **Kubectl**.
|
||||
1. Log out of KubeSphere and log back in as `admin`. Hover your cursor over the hammer icon in the bottom-right corner and then select **Kubectl**.
|
||||
|
||||
2. In the window that appears, run the following command and then navigate to the username and password of the ClickHouse cluster.
|
||||
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@ This tutorial demonstrates how to deploy GitLab on KubeSphere.
|
|||
|
||||
|
||||
|
||||
2. Click the Secret to go to its detail page, and then click the eye 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 the eye icon in the upper-right corner to view the password. Make sure you copy it.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial demonstrates how to deploy TiDB Operator and a TiDB Cluster on Kub
|
|||
|
||||
### Step 1: Install TiDB Operator CRD
|
||||
|
||||
1. Log in to the KubeSphere Web console as `admin`, and use **Kubectl** from the **Toolbox** in the bottom right corner to execute the following command to install TiDB Operator CRD:
|
||||
1. Log in to the KubeSphere Web console as `admin`, and use **Kubectl** from the **Toolbox** in the bottom-right corner to execute the following command to install TiDB Operator CRD:
|
||||
|
||||
```bash
|
||||
kubectl apply -f https://raw.githubusercontent.com/pingcap/tidb-operator/v1.1.6/manifests/crd.yaml
|
||||
|
|
@ -71,7 +71,7 @@ This tutorial demonstrates how to deploy TiDB Operator and a TiDB Cluster on Kub
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
4. On the **Chart Files** tab, you can view the configuration from the console directly or download the default `values.yaml` file by clicking the icon in the upper right corner. Under **Versions**, select a version number from the drop-down list and click **Deploy**.
|
||||
4. On the **Chart Files** tab, you can view the configuration from the console directly or download the default `values.yaml` file by clicking the icon in the upper-right corner. Under **Versions**, select a version number from the drop-down list and click **Deploy**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
## Resource Usage
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This guide demonstrates how to set cluster visibility.
|
|||
|
||||
1. Log in to KubeSphere with an account that has the permission to create a workspace, such as `ws-manager`.
|
||||
|
||||
2. Click **Platform** in the top left corner and select **Access Control**. In **Workspaces** from the navigation bar, click **Create**.
|
||||
2. Click **Platform** in the top-left corner and select **Access Control**. In **Workspaces** from the navigation bar, click **Create**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -46,7 +46,7 @@ After a workspace is created, you can allocate additional clusters to the worksp
|
|||
|
||||
1. Log in to KubeSphere with an account that has the permission to manage clusters, such as `admin`.
|
||||
|
||||
2. Click **Platform** in the top left corner and select **Cluster Management**. Select a cluster from the list to view cluster information.
|
||||
2. Click **Platform** in the top-left corner and select **Cluster Management**. Select a cluster from the list to view cluster information.
|
||||
|
||||
3. In **Cluster Settings** from the navigation bar, select **Cluster Visibility**.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ You can use Elasticsearch, Kafka and Fluentd as log receivers in KubeSphere. Thi
|
|||
|
||||
## Add Elasticsearch as a Receiver
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
@ -33,5 +33,5 @@ If you have enabled the [multi-cluster feature](../../../../multicluster-managem
|
|||
|
||||
5. Elasticsearch will appear in the receiver list on the **Log Collection** page, the status of which is **Collecting**.
|
||||
|
||||
6. To verify whether Elasticsearch is receiving logs sent from Fluent Bit, click **Log Search** in the **Toolbox** in the bottom right corner and search logs on the console. For more information, read [Log Query](../../../../toolbox/log-query/).
|
||||
6. To verify whether Elasticsearch is receiving logs sent from Fluent Bit, click **Log Search** in the **Toolbox** in the bottom-right corner and search logs on the console. For more information, read [Log Query](../../../../toolbox/log-query/).
|
||||
|
||||
|
|
|
|||
|
|
@ -122,7 +122,7 @@ EOF
|
|||
|
||||
## Step 2: Add Fluentd as a Log Receiver
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -101,7 +101,7 @@ You can use [strimzi-kafka-operator](https://github.com/strimzi/strimzi-kafka-op
|
|||
|
||||
## Step 2: Add Kafka as a Log Receiver
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ To add a log receiver:
|
|||
|
||||
1. Log in to the web console of KubeSphere as `admin`.
|
||||
|
||||
2. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
2. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
## Cluster Status Monitoring
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
|
||||
{{< notice tip >}}
|
||||
You can customize the time range from the drop-down list in the top right corner to view historical data.
|
||||
You can customize the time range from the drop-down list in the top-right corner to view historical data.
|
||||
{{</ notice >}}
|
||||
|
||||
### Component status
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ KubeSphere also has built-in policies which will trigger alerts if conditions de
|
|||
|
||||
## Create an Alerting Policy
|
||||
|
||||
1. Log in to the console as `cluster-admin`. Click **Platform** in the top left corner, and then click **Cluster Management**.
|
||||
1. Log in to the console as `cluster-admin`. Click **Platform** in the top-left corner, and then click **Cluster Management**.
|
||||
|
||||
2. Navigate to **Alerting Policies** under **Monitoring & Alerting**, and then click **Create**.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
Cluster nodes are only accessible to cluster administrators. Some node metrics are very important to clusters. Therefore, it is the administrator's responsibility to watch over these numbers and make sure nodes are available. Follow the steps below to view node status.
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
## Manage Storage Classes
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -54,7 +54,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
### Common settings
|
||||
|
||||
Some settings are commonly used and shared among storage classes. You can find them as dashboard properties on the console, which are also indicated by fields or annotations in the StorageClass manifest. You can see the manifest file in YAML format by enabling **Edit Mode** in the top right corner.
|
||||
Some settings are commonly used and shared among storage classes. You can find them as dashboard properties on the console, which are also indicated by fields or annotations in the StorageClass manifest. You can see the manifest file in YAML format by enabling **Edit Mode** in the top-right corner.
|
||||
Here are property descriptions of some commonly used fields in KubeSphere.
|
||||
|
||||
| Property | Description |
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ This tutorial demonstrates how to configure your email server and add recipients
|
|||
|
||||
1. Log in to the web console with an account granted the role `platform-admin`.
|
||||
|
||||
2. Click **Platform** in the top left corner and select **Platform Settings**.
|
||||
2. Click **Platform** in the top-left corner and select **Platform Settings**.
|
||||
|
||||
3. Navigate to **Email** under **Notification Management**.
|
||||
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ You must provide the Slack token on the console for authentication so that KubeS
|
|||
|
||||
1. Log in to the web console with an account granted the role `platform-admin`.
|
||||
|
||||
2. Click **Platform** in the top left corner and select **Platform Settings**.
|
||||
2. Click **Platform** in the top-left corner and select **Platform Settings**.
|
||||
|
||||
3. Navigate to **Slack** under **Notification Management**.
|
||||
|
||||
|
|
|
|||
|
|
@ -243,7 +243,7 @@ You must create the projects as shown in the table below in advance. Make sure y
|
|||
|
||||
|
||||
|
||||
3. Check the pipeline running logs by clicking **Show Logs** in the upper right corner. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
3. Check the pipeline running logs by clicking **Show Logs** in the upper-right corner. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ weight: 11410
|
|||
|
||||
## Create a Docker Hub Access Token
|
||||
|
||||
1. Log in to [Docker Hub](https://hub.docker.com/) and select **Account Settings** from the menu in the top right corner.
|
||||
1. Log in to [Docker Hub](https://hub.docker.com/) and select **Account Settings** from the menu in the top-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ weight: 11420
|
|||
|
||||
## Create a Docker Hub Access Token
|
||||
|
||||
1. Log in to [Docker Hub](https://hub.docker.com/) and select **Account Settings** from the menu in the top right corner.
|
||||
1. Log in to [Docker Hub](https://hub.docker.com/) and select **Account Settings** from the menu in the top-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
|
||||
|
||||
3. Click **Log in** in the top right corner and use the default account `admin/admin`.
|
||||
3. Click **Log in** in the top-right corner and use the default account `admin/admin`.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -330,7 +330,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
5. When you finish the steps above, click **Confirm** and **Save** in the bottom right corner. You can see the pipeline now has a complete workflow with each stage clearly listed on the pipeline. When you define a pipeline using the graphical editing panel, KubeSphere automatically creates its corresponding Jenkinsfile. Click **Edit Jenkinsfile** to view the Jenkinsfile.
|
||||
5. When you finish the steps above, click **Confirm** and **Save** in the bottom-right corner. You can see the pipeline now has a complete workflow with each stage clearly listed on the pipeline. When you define a pipeline using the graphical editing panel, KubeSphere automatically creates its corresponding Jenkinsfile. Click **Edit Jenkinsfile** to view the Jenkinsfile.
|
||||
|
||||
|
||||
|
||||
|
|
@ -362,7 +362,7 @@ This stage uses SonarQube to test your code. You can skip this stage if you do n
|
|||
|
||||
|
||||
|
||||
3. Click **Show Logs** in the top right corner to inspect all the logs. Click each stage to see detailed logs of it. You can debug any problems based on the logs which also can be downloaded locally for further analysis.
|
||||
3. Click **Show Logs** in the top-right corner to inspect all the logs. Click each stage to see detailed logs of it. You can debug any problems based on the logs which also can be downloaded locally for further analysis.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -267,7 +267,7 @@ The account `project-admin` needs to be created in advance since it is the revie
|
|||
|
||||
|
||||
|
||||
2. Check the pipeline running logs by clicking **Show Logs** in the top right corner. You can see the dynamic log output of the pipeline, including any errors that may stop the pipeline from running. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
2. Check the pipeline running logs by clicking **Show Logs** in the top-right corner. You can see the dynamic log output of the pipeline, including any errors that may stop the pipeline from running. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
|
||||
|
||||
|
||||
|
|
@ -316,7 +316,7 @@ The account `project-admin` needs to be created in advance since it is the revie
|
|||
|
||||
|
||||
|
||||
2. Use the **web kubectl** from **Toolbox** in the bottom right corner by executing the following command:
|
||||
2. Use the **web kubectl** from **Toolbox** in the bottom-right corner by executing the following command:
|
||||
|
||||
```bash
|
||||
curl 10.233.120.230:8080
|
||||
|
|
|
|||
|
|
@ -84,7 +84,7 @@ You need to create two projects, such as `kubesphere-sample-dev` and `kubesphere
|
|||
|
||||
|
||||
|
||||
3. In the **GitLab** tab, select the default option `https://gitlab.com` for GitLab Server, enter the username of the GitLab project owner for **Owner**, and then select the `devops-java-sample` repository from the drop-down list for **Repository Name**. Click the tick icon in the bottom right corner and then click **Next**.
|
||||
3. In the **GitLab** tab, select the default option `https://gitlab.com` for GitLab Server, enter the username of the GitLab project owner for **Owner**, and then select the `devops-java-sample` repository from the drop-down list for **Repository Name**. Click the tick icon in the bottom-right corner and then click **Next**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -122,7 +122,7 @@ You need to create two projects, such as `kubesphere-sample-dev` and `kubesphere
|
|||
|
||||
### Step 6: Check the pipeline status
|
||||
|
||||
1. In the **Task Status** tab, you can see how a pipeline is running. Check the pipeline running logs by clicking **Show Logs** in the top right corner.
|
||||
1. In the **Task Status** tab, you can see how a pipeline is running. Check the pipeline running logs by clicking **Show Logs** in the top-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ The built-in Jenkins cannot share the same email configuration with the platform
|
|||
|
||||
## Set the Email Server
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ You have enabled [the KubeSphere DevOps System](../../../pluggable-components/de
|
|||
|
||||
It is recommended that you configure Jenkins in KubeSphere through Configuration-as-Code (CasC). The built-in Jenkins CasC file is stored as a [ConfigMap](../../../project-user-guide/configuration/configmaps/).
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to KubeSphere as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ You need an account granted a role including the authorization of **Cluster Mana
|
|||
|
||||
## Label a CI Node
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ As an open-source and app-centric container platform, KubeSphere integrates 16 b
|
|||
|
||||
## Remove a Built-in App
|
||||
|
||||
1. Log in to the web console of KubeSphere as `admin`, click **Platform** in the upper left corner, and then select **App Store Management**.
|
||||
1. Log in to the web console of KubeSphere as `admin`, click **Platform** in the upper-left corner, and then select **App Store Management**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ To deploy an app in KubeSphere, tenants can go to the App Store and select the a
|
|||
|
||||
### Reuse the same app name
|
||||
|
||||
1. If you try to deploy a new Redis app with the same app name as `redis-1`, you can see the following error prompt in the upper right corner.
|
||||
1. If you try to deploy a new Redis app with the same app name as `redis-1`, you can see the following error prompt in the upper-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ You have installed KubeSphere.
|
|||
|
||||
## Change the Console Language
|
||||
|
||||
1. Log in to KubeSphere with your account and click the account name in the top right corner.
|
||||
1. Log in to KubeSphere with your account and click the account name in the top-right corner.
|
||||
|
||||
2. Select **User Settings**.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Editing resources in `system-workspace` may cause unexpected results, such as Ku
|
|||
|
||||
## Edit the Console Configuration
|
||||
|
||||
1. Log in to KubeSphere as `admin`. Click the hammer icon in the bottom right corner and select **Kubectl**.
|
||||
1. Log in to KubeSphere as `admin`. Click the hammer icon in the bottom-right corner and select **Kubectl**.
|
||||
|
||||
2. Execute the following command:
|
||||
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ You need to enable [the KubeSphere DevOps system](../../../pluggable-components/
|
|||
|
||||
|
||||
|
||||
3. Select the **Available** tab and you can see all the available plugins listed on the page. You can also use the **Filter** in the upper right corner to search for the plugins you need. Check the checkbox next to the plugin you need, and then click **Install without restart** or **Download now and install after restart** based on your needs.
|
||||
3. Select the **Available** tab and you can see all the available plugins listed on the page. You can also use the **Filter** in the upper-right corner to search for the plugins you need. Check the checkbox next to the plugin you need, and then click **Install without restart** or **Download now and install after restart** based on your needs.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ If you install KubeSphere on Linux, see [Disable Telemetry after Installation](.
|
|||
|
||||
### Disable Telemetry after installation
|
||||
|
||||
1. Log in to the console as `admin` and click **Platform** in the top left corner.
|
||||
1. Log in to the console as `admin` and click **Platform** in the top-left corner.
|
||||
|
||||
2. Select **Cluster Management** and navigate to **CRDs**.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ Azure can help you implement infrastructure as code by providing resource deploy
|
|||
|
||||
### Use Azure Cloud Shell
|
||||
|
||||
You don't have to install Azure CLI on your machine as Azure provides a web-based terminal. Click the Cloud Shell button on the menu bar at the upper right corner in Azure portal.
|
||||
You don't have to install Azure CLI on your machine as Azure provides a web-based terminal. Click the Cloud Shell button on the menu bar at the upper-right corner in Azure portal.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ To make sure edge nodes can successfully talk to your cluster, you must forward
|
|||
|
||||
## Add an Edge Node
|
||||
|
||||
1. Log in to the console as `admin` and click **Platform** in the top left corner.
|
||||
1. Log in to the console as `admin` and click **Platform** in the top-left corner.
|
||||
|
||||
2. Select **Cluster Management** and navigate to **Edge Nodes** under **Node Management**.
|
||||
|
||||
|
|
|
|||
|
|
@ -77,7 +77,7 @@ You can follow the New Virtual Machine wizard to create a virtual machine to pla
|
|||
|
||||
|
||||
|
||||
6. In **Ready to complete** page, you review the configuration selections that you have made for the virtual machine. Click **Finish** at the bottom right corner to continue.
|
||||
6. In **Ready to complete** page, you review the configuration selections that you have made for the virtual machine. Click **Finish** at the bottom-right corner to continue.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -284,7 +284,7 @@ glusterfs (default) kubernetes.io/glusterfs Delete Immediate
|
|||
|
||||
### KubeSphere console
|
||||
|
||||
1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
3. Go to **Volumes** under **Storage**, and you can see PVCs in use.
|
||||
|
||||
|
|
|
|||
|
|
@ -256,7 +256,7 @@ You can verify that NFS-client has been successfully installed either from the c
|
|||
|
||||
### KubeSphere console
|
||||
|
||||
1. Log in to the web console as `admin` with the default account and password at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to the web console as `admin` with the default account and password at `<NodeIP>:30880`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
2. Go to **Pods** in **Application Workloads** and select `kube-system` from the project drop-down list. You can see that the Pod of `nfs-client` is up and running.
|
||||
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@ Your cluster nodes are created on [QingCloud Platform](https://intl.qingcloud.co
|
|||
|
||||
To make sure the platform can create cloud disks for your cluster, you need to provide the access key (`qy_access_key_id` and `qy_secret_access_key`) in a separate configuration file of QingCloud CSI.
|
||||
|
||||
1. Log in to the web console of [QingCloud](https://console.qingcloud.com/login) and select **Access Key** from the drop-down list in the top right corner.
|
||||
1. Log in to the web console of [QingCloud](https://console.qingcloud.com/login) and select **Access Key** from the drop-down list in the top-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
@ -261,7 +261,7 @@ You can verify that QingCloud CSI has been successfully installed either from th
|
|||
|
||||
### KubeSphere console
|
||||
|
||||
1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Log in to the web console with the default account and password (`admin/P@88w0rd`) at `<NodeIP>:30880`. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
2. Go to **Pods** in **Application Workloads** and select `kube-system` from the project drop-down list. You can see that the Pods of `csi-qingcloud` are up and running.
|
||||
|
||||
|
|
|
|||
|
|
@ -227,7 +227,7 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
|
||||
|
||||
2. Enter the basic information of the cluster to be imported on the **Import Cluster** page. You can also click **Edit Mode** in the top right corner to view and edit the basic information in YAML format. After you finish editing, click **Next**.
|
||||
2. Enter the basic information of the cluster to be imported on the **Import Cluster** page. You can also click **Edit Mode** in the top-right corner to view and edit the basic information in YAML format. After you finish editing, click **Next**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -154,11 +154,11 @@ kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=
|
|||
|
||||
|
||||
|
||||
2. Enter the basic information of the cluster to be imported on the **Import Cluster** page. You can also click **Edit Mode** in the top right corner to view and edit the basic information in YAML format. After you finish editing, click **Next**.
|
||||
2. Enter the basic information of the cluster to be imported on the **Import Cluster** page. You can also click **Edit Mode** in the top-right corner to view and edit the basic information in YAML format. After you finish editing, click **Next**.
|
||||
|
||||
|
||||
|
||||
3. In **Connection Method**, select **Direct Connection**, and copy the kubeconfig of the Member Cluster and paste it into the box. You can also click **Edit Mode** in the top right corner to edit the kubeconfig of the Member Cluster in YAML format.
|
||||
3. In **Connection Method**, select **Direct Connection**, and copy the kubeconfig of the Member Cluster and paste it into the box. You can also click **Edit Mode** in the top-right corner to edit the kubeconfig of the Member Cluster in YAML format.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -29,7 +29,7 @@ This tutorial demonstrates how to import an Aliyun ACK cluster through the [dire
|
|||
jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
|
||||
```
|
||||
|
||||
2. Log in to the KubeSphere console of the ACK cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
|
||||
2. Log in to the KubeSphere console of the ACK cluster as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**.
|
||||
|
||||
3. Go to **CRDs**, enter `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
|
||||
|
||||
|
|
@ -65,7 +65,7 @@ Log in to the web console of Aliyun. Go to **Clusters** under **Container Servic
|
|||
|
||||
### Step 3: Import the ACK Member Cluster
|
||||
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ You need to deploy KubeSphere on your EKS cluster first. For more information ab
|
|||
jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
|
||||
```
|
||||
|
||||
2. Log in to the KubeSphere console of the EKS cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
|
||||
2. Log in to the KubeSphere console of the EKS cluster as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**.
|
||||
|
||||
3. Go to **CRDs**, enter `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
|
||||
|
||||
|
|
@ -166,7 +166,7 @@ You need to deploy KubeSphere on your EKS cluster first. For more information ab
|
|||
|
||||
### Step 4: Import the EKS Member Cluster
|
||||
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ You need to deploy KubeSphere on your GKE cluster first. For more information ab
|
|||
jwtSecret: "QVguGh7qnURywHn2od9IiOX6X8f8wK8g"
|
||||
```
|
||||
|
||||
2. Log in to the KubeSphere console on GKE as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**.
|
||||
2. Log in to the KubeSphere console on GKE as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**.
|
||||
|
||||
3. Go to **CRDs**, enter `ClusterConfiguration` in the search bar, and then press **Enter** on your keyboard. Click **ClusterConfiguration** to go to its detail page.
|
||||
|
||||
|
|
@ -111,7 +111,7 @@ You need to deploy KubeSphere on your GKE cluster first. For more information ab
|
|||
|
||||
### Step 4: Import the GKE Member Cluster
|
||||
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
1. Log in to the KubeSphere console on your Host Cluster as `admin`. Click **Platform** in the upper-left corner and then select **Cluster Management**. On the **Cluster Management** page, click **Add Cluster**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ This tutorial demonstrates how to unbind a cluster from the central control plan
|
|||
|
||||
## Unbind a Cluster
|
||||
|
||||
1. Click **Platform** in the top left corner and select **Cluster Management**.
|
||||
1. Click **Platform** in the top-left corner and select **Cluster Management**.
|
||||
|
||||
2. On the **Cluster Management** page, click the cluster that you want to remove from the central control plane.
|
||||
|
||||
|
|
|
|||
|
|
@ -106,7 +106,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
## Verify the Installation of the Component
|
||||
|
||||
After you log in to the console, if you can see **App Store** in the top left corner and 16 built-in apps in it, it means the installation is successful.
|
||||
After you log in to the console, if you can see **App Store** in the top-left corner and 16 built-in apps in it, it means the installation is successful.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -148,7 +148,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
{{< tab "Verify the component on the dashboard" >}}
|
||||
|
||||
Verify that you can use the **Auditing Operating** function from the **Toolbox** in the bottom right corner.
|
||||
Verify that you can use the **Auditing Operating** function from the **Toolbox** in the bottom-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -154,7 +154,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
|
|||
|
||||
{{< tab "Verify the component on the dashboard" >}}
|
||||
|
||||
Verify that you can use the **Event Search** function from the **Toolbox** in the bottom right corner.
|
||||
Verify that you can use the **Event Search** function from the **Toolbox** in the bottom-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -85,7 +85,7 @@ This tutorial demonstrates how to collect disk logs for an example app.
|
|||
|
||||
|
||||
|
||||
3. Alternatively, you can also use the **Log Search** function from **Toolbox** in the bottom right corner to view stdout logs. For example, use the Pod name of the Deployment for a fuzzy query:
|
||||
3. Alternatively, you can also use the **Log Search** function from **Toolbox** in the bottom-right corner to view stdout logs. For example, use the Pod name of the Deployment for a fuzzy query:
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ When you create Deployments, StatefulSets or DaemonSets, you need to specify a c
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can enable **Edit Mode** in the top right corner to see corresponding values in the manifest file (YAML format) of properties on the dashboard.
|
||||
You can enable **Edit Mode** in the top-right corner to see corresponding values in the manifest file (YAML format) of properties on the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -274,7 +274,7 @@ A security context defines privilege and access control settings for a Pod or Co
|
|||
|
||||
### Deployment Mode
|
||||
|
||||
You can select different deployment modes to switch between inter-pod affinity and inter-pod anti-affinity. In Kubernetes, inter-pod affinity is specified as field `podAffinity` of field `affinity` while inter-pod anti-affinity is specified as field `podAntiAffinity` of field `affinity`. In KubeSphere, both `podAffinity` and `podAntiAffinity` are set to `preferredDuringSchedulingIgnoredDuringExecution`. You can enable **Edit Mode** in the top right corner to see field details.
|
||||
You can select different deployment modes to switch between inter-pod affinity and inter-pod anti-affinity. In Kubernetes, inter-pod affinity is specified as field `podAffinity` of field `affinity` while inter-pod anti-affinity is specified as field `podAntiAffinity` of field `affinity`. In KubeSphere, both `podAffinity` and `podAntiAffinity` are set to `preferredDuringSchedulingIgnoredDuringExecution`. You can enable **Edit Mode** in the top-right corner to see field details.
|
||||
|
||||
- **Pod Decentralized Deployment** represents anti-affinity.
|
||||
- **Pod Aggregation Deployment** represents affinity.
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Enter the basic information. You can refer to the image below for each field. Wh
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can enable **Edit Mode** in the top right corner to see the YAML manifest of this CronJob.
|
||||
You can enable **Edit Mode** in the top-right corner to see the YAML manifest of this CronJob.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Specify a name for the DaemonSet (for example, `demo-daemonset`) and click **Nex
|
|||
|
||||
5. Select a policy for image pulling from the drop-down menu. For more information, see [Image Pull Policy in Container Image Settings](../container-image-settings/#add-container-image).
|
||||
|
||||
6. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom right corner to continue.
|
||||
6. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom-right corner to continue.
|
||||
|
||||
7. Select an update strategy from the drop-down menu. It is recommended you choose **RollingUpdate**. For more information, see [Update Strategy](../container-image-settings/#update-strategy).
|
||||
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ Specify a name for the Deployment (for example, `demo-deployment`) and click **N
|
|||
1. Before you set an image, define the number of replicated Pods in **Pod Replicas** by clicking the **plus** or **minus** icon, which is indicated by the `.spec.replicas` field in the manifest file.
|
||||
|
||||
{{< notice tip >}}
|
||||
You can see the Deployment manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a Deployment. Alternatively, you can follow the steps below to create a Deployment via the dashboard.
|
||||
You can see the Deployment manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a Deployment. Alternatively, you can follow the steps below to create a Deployment via the dashboard.
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
|
@ -62,7 +62,7 @@ You can see the Deployment manifest file in YAML format by enabling **Edit Mode*
|
|||
|
||||
6. Select a policy for image pulling from the drop-down menu. For more information, see [Image Pull Policy in Container Image Settings](../container-image-settings/#add-container-image).
|
||||
|
||||
7. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom right corner to continue.
|
||||
7. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom-right corner to continue.
|
||||
|
||||
8. Select an update strategy from the drop-down menu. It is recommended you choose **RollingUpdate**. For more information, see [Update Strategy](../container-image-settings/#update-strategy).
|
||||
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ You can set the values in this step as below or click **Next** to use the defaul
|
|||
|
||||
|
||||
|
||||
3. On the same page, scroll down to **Start Command**. Enter the following commands in the box which computes pi to 2000 places then prints it. Click **√** in the bottom right corner and select **Next** to continue.
|
||||
3. On the same page, scroll down to **Start Command**. Enter the following commands in the box which computes pi to 2000 places then prints it. Click **√** in the bottom-right corner and select **Next** to continue.
|
||||
|
||||
```bash
|
||||
perl,-Mbignum=bpi,-wle,print bpi(2000)
|
||||
|
|
@ -76,7 +76,7 @@ For more information about setting images, see [Container Image Settings](../con
|
|||
|
||||
### Step 5: Inspect the Job manifest (optional)
|
||||
|
||||
1. Enable **Edit Mode** in the top right corner which displays the manifest file of the Job. You can see all the values are set based on what you have specified in the previous steps.
|
||||
1. Enable **Edit Mode** in the top-right corner which displays the manifest file of the Job. You can see all the values are set based on what you have specified in the previous steps.
|
||||
|
||||
```yaml
|
||||
apiVersion: batch/v1
|
||||
|
|
|
|||
|
|
@ -90,7 +90,7 @@ The steps of creating a stateful Service and a stateless Service are basically t
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
The value of **Name** is used in both configurations, one for Deployment and the other for Service. You can see the manifest file of the Deployment and the Service by enabling **Edit Mode** in the top right corner. Below is an example file for your reference.
|
||||
The value of **Name** is used in both configurations, one for Deployment and the other for Service. You can see the manifest file of the Deployment and the Service by enabling **Edit Mode** in the top-right corner. Below is an example file for your reference.
|
||||
|
||||
{{</ notice>}}
|
||||
|
||||
|
|
|
|||
|
|
@ -47,7 +47,7 @@ Specify a name for the StatefulSet (for example, `demo-stateful`) and click **Ne
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can see the StatefulSet manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a StatefulSet. Alternatively, you can follow the steps below to create a StatefulSet via the dashboard.
|
||||
You can see the StatefulSet manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a StatefulSet. Alternatively, you can follow the steps below to create a StatefulSet via the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ You can see the StatefulSet manifest file in YAML format by enabling **Edit Mode
|
|||
|
||||
6. Select a policy for image pulling from the drop-down menu. For more information, see [Image Pull Policy in Container Image Settings](../container-image-settings/#add-container-image).
|
||||
|
||||
7. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom right corner to continue.
|
||||
7. For other settings (**Health Checker**, **Start Command**, **Environment Variables**, **Container Security Context** and **Sync Host Timezone**), you can configure them on the dashboard as well. For more information, see detailed explanations of these properties in [Container Image Settings](../container-image-settings/#add-container-image). When you finish, click **√** in the bottom-right corner to continue.
|
||||
|
||||
8. Select an update strategy from the drop-down menu. It is recommended you choose **RollingUpdate**. For more information, see [Update Strategy](../container-image-settings/#update-strategy).
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@ This tutorial demonstrates how to create a microservices-based app Bookinfo, whi
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can create a Service on the dashboard directly or enable **Edit Mode** in the top right corner to edit the YAML file.
|
||||
You can create a Service on the dashboard directly or enable **Edit Mode** in the top-right corner to edit the YAML file.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ This tutorial demonstrates how to create a microservices-based app Bookinfo, whi
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
6. Click **Use Default Ports**. For more information about image settings, see [Container Image Settings](../../../project-user-guide/application-workloads/container-image-settings/). Click **√** in the bottom right corner and **Next** to continue.
|
||||
6. Click **Use Default Ports**. For more information about image settings, see [Container Image Settings](../../../project-user-guide/application-workloads/container-image-settings/). Click **√** in the bottom-right corner and **Next** to continue.
|
||||
|
||||
7. On the **Mount Volumes** page, [add a volume](../../../project-user-guide/storage/volumes/) or click **Next** to continue.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ This tutorial demonstrates how to quickly deploy [NGINX](https://www.nginx.com/)
|
|||
|
||||
### Step 1: Deploy NGINX from the App Store
|
||||
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top left corner.
|
||||
1. On the **Overview** page of the project `demo-project`, click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -26,7 +26,7 @@ You need to create a workspace, a project and an account (`project-regular`). Th
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can see the ConfigMap manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a ConfigMap. Alternatively, you can follow the steps below to create a ConfigMap via the dashboard.
|
||||
You can see the ConfigMap manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a ConfigMap. Alternatively, you can follow the steps below to create a ConfigMap via the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ You can see the ConfigMap manifest file in YAML format by enabling **Edit Mode**
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
5. Click **√** in the bottom right corner to save it and click **Add Data** again if you want to add more key-value pairs.
|
||||
5. Click **√** in the bottom-right corner to save it and click **Add Data** again if you want to add more key-value pairs.
|
||||
|
||||
6. Click **Create** to generate the ConfigMap.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ Specify a name for the Secret (for example, `demo-registry-secret`) and click **
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can see the Secret's manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a Secret. Alternatively, you can follow the steps below to create a Secret via the dashboard.
|
||||
You can see the Secret's manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a Secret. Alternatively, you can follow the steps below to create a Secret via the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Specify a name for the Secret (for example, `demo-secret`) and click **Next** to
|
|||
|
||||
{{< notice tip >}}
|
||||
|
||||
You can see the Secret's manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a Secret. Alternatively, you can follow the steps below to create a Secret via the dashboard.
|
||||
You can see the Secret's manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a Secret. Alternatively, you can follow the steps below to create a Secret via the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
@ -76,7 +76,7 @@ You can see the Secret's manifest file in YAML format by enabling **Edit Mode**
|
|||
|
||||
|
||||
|
||||
3. Click **√** in the bottom right corner to confirm. You can continue to add key-value pairs to the Secret or click **Create** to finish the creation. For more information about how to use the Secret, see [Compose and Deploy WordPress](../../../quick-start/wordpress-deployment/#task-3-create-an-application).
|
||||
3. Click **√** in the bottom-right corner to confirm. You can continue to add key-value pairs to the Secret or click **Create** to finish the creation. For more information about how to use the Secret, see [Compose and Deploy WordPress](../../../quick-start/wordpress-deployment/#task-3-create-an-application).
|
||||
|
||||
## Check Secret Details
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This tutorial walks you through an example of how to monitor MySQL metrics and v
|
|||
|
||||
To begin with, you [deploy MySQL from the App Store](../../../../application-store/built-in-apps/mysql-app/) and set the root password to `testing`.
|
||||
|
||||
1. Go to the project `demo` and click **App Store** in the top left corner.
|
||||
1. Go to the project `demo` and click **App Store** in the top-left corner.
|
||||
|
||||
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ After about two minutes, you can create a monitoring dashboard for MySQL and vis
|
|||
|
||||
|
||||
|
||||
3. Save the template by clicking **Save Template** in the top right corner. A newly-created dashboard displays in the dashboard list as below.
|
||||
3. Save the template by clicking **Save Template** in the top-right corner. A newly-created dashboard displays in the dashboard list as below.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ This section guides you on how to create a dashboard from scratch. You will crea
|
|||
|
||||
|
||||
|
||||
3. Enter a title in the top left corner (for example, `Sample Web Overview`).
|
||||
3. Enter a title in the top-left corner (for example, `Sample Web Overview`).
|
||||
|
||||
|
||||
|
||||
|
|
@ -99,7 +99,7 @@ This section guides you on how to create a dashboard from scratch. You will crea
|
|||
|
||||
|
||||
|
||||
5. Type the PromQL expression `myapp_processed_ops_total` in the field **Monitoring Metrics** and give a chart name (for example, `Operation Count`). Click **√** in the bottom right corner to continue.
|
||||
5. Type the PromQL expression `myapp_processed_ops_total` in the field **Monitoring Metrics** and give a chart name (for example, `Operation Count`). Click **√** in the bottom-right corner to continue.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -28,7 +28,7 @@ To start with a blank template, click **Create**.
|
|||
|
||||
### From a YAML file
|
||||
|
||||
Toggle to **Edit Mode** in the top right corner then paste your dashboard YAML file.
|
||||
Toggle to **Edit Mode** in the top-right corner then paste your dashboard YAML file.
|
||||
|
||||
|
||||
|
||||
|
|
@ -62,11 +62,11 @@ You can view chart details in the right-most column. It shows the **max**, **min
|
|||
|
||||
## Edit the monitoring dashboard
|
||||
|
||||
You can modify an existing template by clicking **Edit Template** in the top right corner.
|
||||
You can modify an existing template by clicking **Edit Template** in the top-right corner.
|
||||
|
||||
### Add a chart
|
||||
|
||||
To add text charts, click the **add icon** in the left column. To add charts in the middle column, click **Add Monitoring Item** in the bottom right corner.
|
||||
To add text charts, click the **add icon** in the left column. To add charts in the middle column, click **Add Monitoring Item** in the bottom-right corner.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This tutorial demonstrates how to configure S2I and B2I webhooks.
|
|||
|
||||
### Step 1: Expose the S2I trigger Service
|
||||
|
||||
1. Log in to the KubeSphere web console as `admin`. Click **Platform** in the top left corner and then select **Cluster Management**.
|
||||
1. Log in to the KubeSphere web console as `admin`. Click **Platform** in the top-left corner and then select **Cluster Management**.
|
||||
|
||||
2. In **Services** under **Application Workloads**, select **kubesphere-devops-system** from the drop-down list and click **s2ioperator-trigger-service** to go to its detail page.
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ All the volumes that are created on the **Volumes** page are PersistentVolumeCla
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
You can see the volume's manifest file in YAML format by enabling **Edit Mode** in the top right corner. KubeSphere allows you to edit the manifest file directly to create a volume. Alternatively, you can follow the steps below to create a volume via the dashboard.
|
||||
You can see the volume's manifest file in YAML format by enabling **Edit Mode** in the top-right corner. KubeSphere allows you to edit the manifest file directly to create a volume. Alternatively, you can follow the steps below to create a volume via the dashboard.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -33,7 +33,7 @@ After KubeSphere is installed, you need to add different users with varied roles
|
|||
1. Log in to the web console as `admin` with the default account and password (`admin/P@88w0rd`).
|
||||
|
||||
{{< notice tip >}}
|
||||
For account security, it is highly recommended that you change your password the first time you log in to the console. To change your password, select **User Settings** in the drop-down menu in the top right corner. In **Password Setting**, set a new password. You also can change the console language in **User Settings**.
|
||||
For account security, it is highly recommended that you change your password the first time you log in to the console. To change your password, select **User Settings** in the drop-down menu in the top-right corner. In **Password Setting**, set a new password. You also can change the console language in **User Settings**.
|
||||
{{</ notice >}}
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@ You need to enable [KubeSphere Auditing Logs](../../../pluggable-components/audi
|
|||
|
||||
## Enter the Query Interface
|
||||
|
||||
1. The query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower right corner and select **Auditing Operating**.
|
||||
1. The query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower-right corner and select **Auditing Operating**.
|
||||
|
||||
{{< notice note >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ This guide demonstrates how you can do multi-level, fine-grained event queries t
|
|||
|
||||
## Query Events
|
||||
|
||||
1. The event query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower right corner and select **Event Search**.
|
||||
1. The event query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower-right corner and select **Event Search**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ You need to enable the [KubeSphere Logging System](../../pluggable-components/lo
|
|||
|
||||
## Enter the Log Query Interface
|
||||
|
||||
1. The log query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower right corner and select **Log Search**.
|
||||
1. The log query function is available for all users. Log in to the console with any account, hover over the **Toolbox** in the lower-right corner and select **Log Search**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ KubeSphere metering helps you track resource consumption within a given cluster
|
|||
|
||||
**Cluster Resource Consumption** contains resource usage information of clusters (and nodes included), such as CPU, memory and storage.
|
||||
|
||||
1. Log in to the KubeSphere console as `admin`, click the hammer icon in the bottom right corner and select **Metering and Billing**.
|
||||
1. Log in to the KubeSphere console as `admin`, click the hammer icon in the bottom-right corner and select **Metering and Billing**.
|
||||
|
||||
2. Click **View Consumption** in the **Cluster Resource Consumption** section.
|
||||
|
||||
|
|
@ -55,7 +55,7 @@ KubeSphere metering helps you track resource consumption within a given cluster
|
|||
|
||||
**Workspace (Project) Resource Consumption** contains resource usage information of workspaces (and projects included), such as CPU, memory and storage.
|
||||
|
||||
1. Log in to the KubeSphere console as `admin`, click the hammer icon in the bottom right corner and select **Metering and Billing**.
|
||||
1. Log in to the KubeSphere console as `admin`, click the hammer icon in the bottom-right corner and select **Metering and Billing**.
|
||||
|
||||
2. Click **View Consumption** in the **Workspace (Project) Resource Consumption** section.
|
||||
|
||||
|
|
|
|||
|
|
@ -14,11 +14,11 @@ This tutorial demonstrates how to use web kubectl to operate on and manage clust
|
|||
|
||||
## Use Web Kubectl
|
||||
|
||||
1. Log in to KubeSphere with an account granted the `platform-admin` role, hover over the **Toolbox** in the lower right corner and select **Kubectl**.
|
||||
1. Log in to KubeSphere with an account granted the `platform-admin` role, hover over the **Toolbox** in the lower-right corner and select **Kubectl**.
|
||||
|
||||
|
||||
|
||||
2. You can see the kubectl interface as shown in the pop-up window. If you have enabled the multi-cluster feature, you need to select the target cluster first from the drop-down list in the upper right corner. This drop-down list is not visible if the multi-cluster feature is not enabled.
|
||||
2. You can see the kubectl interface as shown in the pop-up window. If you have enabled the multi-cluster feature, you need to select the target cluster first from the drop-down list in the upper-right corner. This drop-down list is not visible if the multi-cluster feature is not enabled.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -243,7 +243,7 @@ You must create the projects as shown in the table below in advance. Make sure y
|
|||
|
||||
|
||||
|
||||
3. Check the pipeline running logs by clicking **Show Logs** in the upper right corner. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
3. Check the pipeline running logs by clicking **Show Logs** in the upper-right corner. For each stage, you click it to inspect logs, which can be downloaded to your local machine for further analysis.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ This tutorial demonstrates how to configure S2I and B2I webhooks.
|
|||
|
||||
### Step 1: Expose the S2I trigger Service
|
||||
|
||||
1. Log in to the KubeSphere web console as `admin`. Click **Platform** in the top left corner and then select **Cluster Management**.
|
||||
1. Log in to the KubeSphere web console as `admin`. Click **Platform** in the top-left corner and then select **Cluster Management**.
|
||||
|
||||
2. In **Services** under **Application Workloads**, select **kubesphere-devops-system** from the drop-down list and click **s2ioperator-trigger-service** to go to its detail page.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue