mirror of
https://github.com/kubesphere/website.git
synced 2025-12-26 00:12:48 +00:00
Use US spelling of dialog instead of UK spelling of dialogue
Signed-off-by: Sherlock113 <sherlockxu@yunify.com>
This commit is contained in:
Sherlock113
parent
fb32728a4b
commit
451cc396c6
|
|
@ -66,7 +66,7 @@ You need to create two accounts first, one for ISVs (`isv`) and the other (`revi
|
|||
|
||||
{{</ notice >}}
|
||||
|
||||
2. In the dialogue that appears, click **Upload Helm Chart Package** to upload the chart file. Click **OK** to continue.
|
||||
2. In the dialog that appears, click **Upload Helm Chart Package** to upload the chart file. Click **OK** to continue.
|
||||
|
||||
|
||||
|
||||
|
|
@ -179,7 +179,7 @@ After the app is approved, `isv` can release the Redis application to the App St
|
|||
|
||||
|
||||
|
||||
2. Set a name and icon for the category in the dialogue, then click **OK**. For Redis, you can input `Database` for the field **Category Name**.
|
||||
2. Set a name and icon for the category in the dialog, then click **OK**. For Redis, you can input `Database` for the field **Category Name**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -193,7 +193,7 @@ After the app is approved, `isv` can release the Redis application to the App St
|
|||
|
||||
|
||||
|
||||
4. In the dialogue, select the category (**Database**) from the drop-down list and click **OK**.
|
||||
4. In the dialog, select the category (**Database**) from the drop-down list and click **OK**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -261,7 +261,7 @@ You can choose to remove an app entirely from the App Store or suspend a specifi
|
|||
|
||||
|
||||
|
||||
2. On the detail page, click **Suspend App** and select **OK** in the dialogue to confirm the operation to remove the app from the App Store.
|
||||
2. On the detail page, click **Suspend App** and select **OK** in the dialog to confirm the operation to remove the app from the App Store.
|
||||
|
||||
|
||||
|
||||
|
|
@ -275,7 +275,7 @@ You can choose to remove an app entirely from the App Store or suspend a specifi
|
|||
|
||||
|
||||
|
||||
4. To suspend a specific app version, expand the version menu and click **Suspend Version**. In the dialogue that appears, click **OK** to confirm.
|
||||
4. To suspend a specific app version, expand the version menu and click **Suspend Version**. In the dialog that appears, click **OK** to confirm.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -63,7 +63,7 @@ This tutorial walks you through an example of deploying MongoDB from the App Sto
|
|||
|
||||
{{< notice note >}}
|
||||
|
||||
If you want to access MongoDB outside the cluster, click **More** and select **Edit Internet Access**. In the dialogue that appears, select **NodePort** as the access mode. Use the port number to access MongoDB after it is exposed. You may need to open the port in your security groups and configure related port forwarding rules depending on your where your Kubernetes cluster is deployed.
|
||||
If you want to access MongoDB outside the cluster, click **More** and select **Edit Internet Access**. In the dialog that appears, select **NodePort** as the access mode. Use the port number to access MongoDB after it is exposed. You may need to open the port in your security groups and configure related port forwarding rules depending on your where your Kubernetes cluster is deployed.
|
||||
|
||||
{{</ notice >}}
|
||||
|
||||
|
|
|
|||
|
|
@ -38,7 +38,7 @@ You need to create credentials in KubeSphere for the access token created so tha
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, set a **Credential ID**, which will be used later in the Jenkinsfile, and select **Account Credentials** for **Type**. Enter your Docker Hub account name for **Username** and the access token just created for **Token/Password**. When you finish, click **OK**.
|
||||
2. In the dialog that appears, set a **Credential ID**, which will be used later in the Jenkinsfile, and select **Account Credentials** for **Type**. Enter your Docker Hub account name for **Username** and the access token just created for **Token/Password**. When you finish, click **OK**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ You need to create credentials in KubeSphere for the access token created so tha
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, set a **Credential ID**, which will be used later in the Jenkinsfile, and select **Account Credentials** for **Type**. Enter your Docker Hub account name for **Username** and the access token just created for **Token/Password**. When you finish, click **OK**.
|
||||
2. In the dialog that appears, set a **Credential ID**, which will be used later in the Jenkinsfile, and select **Account Credentials** for **Type**. Enter your Docker Hub account name for **Username** and the access token just created for **Token/Password**. When you finish, click **OK**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -138,7 +138,7 @@ To integrate SonarQube into your pipeline, you must install SonarQube Server fir
|
|||
|
||||
|
||||
|
||||
5. Input **Name** and **Jenkins Console URL** (i.e. the SonarQube Webhook address) in the dialogue that appears. Click **Create** to finish.
|
||||
5. Input **Name** and **Jenkins Console URL** (i.e. the SonarQube Webhook address) in the dialog that appears. Click **Create** to finish.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -131,7 +131,7 @@ The account `project-admin` needs to be created in advance since it is the revie
|
|||
|
||||
|
||||
|
||||
2. Provide the basic information in the dialogue that appears. Name it `jenkinsfile-in-scm` and select a code repository.
|
||||
2. Provide the basic information in the dialog that appears. Name it `jenkinsfile-in-scm` and select a code repository.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@ Currently, you can store the following 4 types of credentials in a DevOps projec
|
|||
- **Account Credentials**: Username and password which can be handled as separate components or as a colon-separated string in the format `username:password`, such as accounts of GitHub, GitLab, and Docker Hub.
|
||||
- **SSH**: Username with a private key, an SSH public/private key pair.
|
||||
- **Secret Text**: Secret content in a file.
|
||||
- **kubeconfig**: It is used to configure cross-cluster authentication. If you select this type, the dialogue will auto-populate the field with the kubeconfig file of the current Kubernetes cluster.
|
||||
- **kubeconfig**: It is used to configure cross-cluster authentication. If you select this type, the dialog will auto-populate the field with the kubeconfig file of the current Kubernetes cluster.
|
||||
|
||||
This tutorial demonstrates how to create and manage credentials in a DevOps project. For more information about how credentials are used, see [Create a Pipeline Using a Jenkinsfile](../create-a-pipeline-using-jenkinsfile/) and [Create a Pipeline Using Graphical Editing Panels](../create-a-pipeline-using-graphical-editing-panel).
|
||||
|
||||
|
|
@ -34,7 +34,7 @@ Log in the console of KubeSphere as `project-regular`. Navigate to your DevOps p
|
|||
|
||||
### Create Docker Hub Credentials
|
||||
|
||||
1. In the dialogue that appears, provide the following information.
|
||||
1. In the dialog that appears, provide the following information.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -30,7 +30,7 @@ You need an account granted a role including the authorization of **Clusters Man
|
|||
|
||||
|
||||
|
||||
5. In the dialogue that appears, click **Add Labels**. Add a new label with key `node-role.kubernetes.io/worker` and value `ci`, and click **Save**.
|
||||
5. In the dialog that appears, click **Add Labels**. Add a new label with key `node-role.kubernetes.io/worker` and value `ci`, and click **Save**.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -81,7 +81,7 @@ The steps of creating a stateful Service and a stateless Service are basically t
|
|||
|
||||
### Step 2: Input Basic Information
|
||||
|
||||
1. In the dialogue that appears, you can see the filed **Version** prepopulated with `v1`. You need to define a name for the Service, such as `demo-service`. When you finish, click **Next** to continue.
|
||||
1. In the dialog that appears, you can see the filed **Version** prepopulated with `v1`. You need to define a name for the Service, such as `demo-service`. When you finish, click **Next** to continue.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ This tutorial demonstrates how to quickly deploy [Grafana](https://grafana.com/)
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, enter `test-repo` for the app repository name and `https://helm-chart-repo.pek3a.qingstor.com/kubernetes-charts/` for the repository URL. Click **Validate** to verify the URL and click **OK** to continue.
|
||||
2. In the dialog that appears, enter `test-repo` for the app repository name and `https://helm-chart-repo.pek3a.qingstor.com/kubernetes-charts/` for the repository URL. Click **Validate** to verify the URL and click **OK** to continue.
|
||||
|
||||
|
||||
|
||||
|
|
@ -44,7 +44,7 @@ This tutorial demonstrates how to quickly deploy [Grafana](https://grafana.com/)
|
|||
|
||||
|
||||
|
||||
2. Select **From App Templates** from the pop-up dialogue.
|
||||
2. Select **From App Templates** from the pop-up dialog.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ After about two minutes, you can create a monitoring dashboard for MySQL and vis
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, name the dashboard as `mysql-overview` and choose **MySQL template**. Click **Create** to continue.
|
||||
2. In the dialog that appears, name the dashboard as `mysql-overview` and choose **MySQL template**. Click **Create** to continue.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -25,7 +25,7 @@ This tutorial demonstrates how to add an app repository to KubeSphere.
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, specify an app repository name and add your repository URL. For example, enter `https://charts.kubesphere.io/main`.
|
||||
2. In the dialog that appears, specify an app repository name and add your repository URL. For example, enter `https://charts.kubesphere.io/main`.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ This tutorial demonstrates how to develop an app template by uploading a package
|
|||
|
||||
|
||||
|
||||
2. In the dialogue that appears, click **Upload Helm Chart Package**. You can upload your own Helm chart or download the [Nginx chart](/files/application-templates/nginx-0.1.0.tgz) and use it as an example for the following steps.
|
||||
2. In the dialog that appears, click **Upload Helm Chart Package**. You can upload your own Helm chart or download the [Nginx chart](/files/application-templates/nginx-0.1.0.tgz) and use it as an example for the following steps.
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue