diff --git a/content/en/docs/v3.3/application-store/external-apps/deploy-gitlab.md b/content/en/docs/v3.3/application-store/external-apps/deploy-gitlab.md index 93367b21a..107fae07c 100644 --- a/content/en/docs/v3.3/application-store/external-apps/deploy-gitlab.md +++ b/content/en/docs/v3.3/application-store/external-apps/deploy-gitlab.md @@ -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 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 icon in the upper-right corner to view the password. Make sure you copy it. ### Step 4: Edit the hosts file diff --git a/content/en/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md b/content/en/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md index b608c18c7..81bc94acc 100644 --- a/content/en/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md +++ b/content/en/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md @@ -61,7 +61,7 @@ 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 or 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 icon or 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 diff --git a/content/en/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md b/content/en/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md index 78e9d8e6c..02dbaa54f 100644 --- a/content/en/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md +++ b/content/en/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md @@ -37,7 +37,7 @@ 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 to modify the code segment of `` in the file. Set the `` and use the URLs of your own Nexus repositories. +3. Click icon to modify the code segment of `` in the file. Set the `` and use the URLs of your own Nexus repositories. ![modify-pom](/images/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipeline/modify-pom.png) diff --git a/content/en/docs/v3.3/project-administration/disk-log-collection.md b/content/en/docs/v3.3/project-administration/disk-log-collection.md index 033bdb85b..3cb033174 100644 --- a/content/en/docs/v3.3/project-administration/disk-log-collection.md +++ b/content/en/docs/v3.3/project-administration/disk-log-collection.md @@ -69,7 +69,7 @@ This tutorial demonstrates how to collect logs for an example app. 1. Under the **Deployments** tab, click the Deployment just created to go to its detail page. -2. In **Resource Status**, you can click to view container details, and then click of `logsidecar-container` (filebeat container) to view logs. +2. In **Resource Status**, you can click to view container details, and then click icon of `logsidecar-container` (filebeat container) to view logs. 3. Alternatively, you can also click in the lower-right corner and select **Log Search** to view stdout logs. For example, use the Pod name of the Deployment for a fuzzy query. diff --git a/content/en/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md b/content/en/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md index 61f452a72..f0a78fcae 100644 --- a/content/en/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md +++ b/content/en/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md @@ -18,7 +18,7 @@ You can enable **Edit YAML** in the upper-right corner to see corresponding valu ### Pod Replicas -Set the number of replicated Pods by clicking or , indicated by the `.spec.replicas` field in the manifest file. This option is not available for DaemonSets. +Set the number of replicated Pods by clicking icon or icon, indicated by the `.spec.replicas` field in the manifest file. This option is not available for DaemonSets. If you create Deployments in a multi-cluster project, select a replica scheduling mode under **Replica Scheduling Mode**: @@ -33,7 +33,7 @@ Click **Add Container** to add a container. #### Image Search Box -You can click on the right to select an image from the list or enter an image name to search it. KubeSphere provides Docker Hub images and your private image repository. If you want to use your private image repository, you need to create an Image Registry Secret first in **Secrets** under **Configuration**. +You can click icon on the right to select an image from the list or enter an image name to search it. KubeSphere provides Docker Hub images and your private image repository. If you want to use your private image repository, you need to create an Image Registry Secret first in **Secrets** under **Configuration**. {{< notice note >}} diff --git a/content/en/docs/v3.3/project-user-guide/application-workloads/cronjobs.md b/content/en/docs/v3.3/project-user-guide/application-workloads/cronjobs.md index 8e9a42cb5..4dc4f89de 100644 --- a/content/en/docs/v3.3/project-user-guide/application-workloads/cronjobs.md +++ b/content/en/docs/v3.3/project-user-guide/application-workloads/cronjobs.md @@ -79,7 +79,7 @@ Please refer to [Jobs](../jobs/#step-3-strategy-settings-optional). 3. Click any of them and you will be directed to the Job details page. -4. In **Resource Status**, you can inspect the Pod status. Click on the right and click to check the container log as shown below, which displays the expected output. +4. In **Resource Status**, you can inspect the Pod status. Click icon on the right and click icon to check the container log as shown below, which displays the expected output. ## Check CronJob Details diff --git a/content/en/docs/v3.3/project-user-guide/application-workloads/deployments.md b/content/en/docs/v3.3/project-user-guide/application-workloads/deployments.md index c0fc5c16a..10d30da76 100644 --- a/content/en/docs/v3.3/project-user-guide/application-workloads/deployments.md +++ b/content/en/docs/v3.3/project-user-guide/application-workloads/deployments.md @@ -27,7 +27,7 @@ Specify a name for the Deployment (for example, `demo-deployment`), select a pro ### Step 3: Set a Pod -1. Before you set an image, define the number of replicated Pods in **Pod Replicas** by clicking or , which is indicated by the `.spec.replicas` field in the manifest file. +1. Before you set an image, define the number of replicated Pods in **Pod Replicas** by clicking icon or 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 YAML** in the upper-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. @@ -104,7 +104,7 @@ You can set a policy for node scheduling and add metadata in this section. When 4. Click the **Resource Status** tab to view the port and Pod information of the Deployment. - - **Replica Status**: Click or to increase or decrease the number of Pod replicas. + - **Replica Status**: Click icon or icon to increase or decrease the number of Pod replicas. - **Pods** - The Pod list provides detailed information of the Pod (status, node, Pod IP and resource usage). diff --git a/content/en/docs/v3.3/project-user-guide/application-workloads/jobs.md b/content/en/docs/v3.3/project-user-guide/application-workloads/jobs.md index 3eb576728..1a5f98c44 100644 --- a/content/en/docs/v3.3/project-user-guide/application-workloads/jobs.md +++ b/content/en/docs/v3.3/project-user-guide/application-workloads/jobs.md @@ -115,7 +115,7 @@ You can set the values in this step or click **Next** to use the default values. You can rerun the Job if it fails and the reason for failure is displayed under **Message**. {{}} -3. In **Resource Status**, you can inspect the Pod status. Two Pods were created each time as **Parallel Pods** was set to 2. Click on the right and click to check the container log, which displays the expected calculation result. +3. In **Resource Status**, you can inspect the Pod status. Two Pods were created each time as **Parallel Pods** was set to 2. Click on the right and click icon to check the container log, which displays the expected calculation result. {{< notice tip >}} diff --git a/content/en/docs/v3.3/project-user-guide/application-workloads/statefulsets.md b/content/en/docs/v3.3/project-user-guide/application-workloads/statefulsets.md index 21111b5a1..568f92ef9 100644 --- a/content/en/docs/v3.3/project-user-guide/application-workloads/statefulsets.md +++ b/content/en/docs/v3.3/project-user-guide/application-workloads/statefulsets.md @@ -39,7 +39,7 @@ Specify a name for the StatefulSet (for example, `demo-stateful`), select a proj ### Step 3: Set a Pod -1. Before you set an image, define the number of replicated Pods in **Pod Replicas** by clicking or , which is indicated by the `.spec.replicas` field in the manifest file. +1. Before you set an image, define the number of replicated Pods in **Pod Replicas** by clicking icon or icon, which is indicated by the `.spec.replicas` field in the manifest file. {{< notice tip >}} @@ -112,7 +112,7 @@ You can set a policy for node scheduling and add StatefulSet metadata in this se 4. Click the **Resource Status** tab to view the port and Pod information of a StatefulSet. - - **Replica Status**: Click or to increase or decrease the number of Pod replicas. + - **Replica Status**: Click icon or icon to increase or decrease the number of Pod replicas. - **Pods** - The Pod list provides detailed information of the Pod (status, node, Pod IP and resource usage). diff --git a/content/en/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md b/content/en/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md index dfa537bcc..1e74c3dde 100644 --- a/content/en/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md +++ b/content/en/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md @@ -61,7 +61,7 @@ This section guides you on how to create a dashboard from scratch. You will crea 3. Enter a title in the upper-left corner (for example, `Sample Web Overview`). -4. Click on the left column to create a text chart. +4. Click icon on the left column to create a text chart. 5. Type the PromQL expression `myapp_processed_ops_total` in the field **Monitoring Metric** and give a chart name (for example, `Operation Count`). Click **√** in the lower-right corner to continue. diff --git a/content/en/docs/v3.3/quick-start/create-workspace-and-project.md b/content/en/docs/v3.3/quick-start/create-workspace-and-project.md index 600c35c43..84448b7b8 100644 --- a/content/en/docs/v3.3/quick-start/create-workspace-and-project.md +++ b/content/en/docs/v3.3/quick-start/create-workspace-and-project.md @@ -219,7 +219,7 @@ After you finish the above steps, you know that users can be granted different r {{}} -5. On the **Platform Roles** page, you can click the name of the created role to view the role details and click to edit the role, edit the role permissions, or delete the role. +5. On the **Platform Roles** page, you can click the name of the created role to view the role details and click icon to edit the role, edit the role permissions, or delete the role. 6. On the **Users** page, you can assign the role to a user when you create a user or edit an existing user. diff --git a/content/en/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md b/content/en/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md index da9ef6bc6..2d058ba5a 100644 --- a/content/en/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md +++ b/content/en/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md @@ -48,7 +48,7 @@ The following figure shows the end-to-end architecture of the application. For m {{< notice note >}} -KubeSphere creates the hostname automatically. To change the hostname, hover over the default route rule and click to edit it. For more information, see [Create a Microservices-based App](../../project-user-guide/application/compose-app/). +KubeSphere creates the hostname automatically. To change the hostname, hover over the default route rule and click icon to edit it. For more information, see [Create a Microservices-based App](../../project-user-guide/application/compose-app/). {{}} diff --git a/content/zh/docs/v3.3/application-store/external-apps/deploy-gitlab.md b/content/zh/docs/v3.3/application-store/external-apps/deploy-gitlab.md index 5de1ba803..8218aeb18 100644 --- a/content/zh/docs/v3.3/application-store/external-apps/deploy-gitlab.md +++ b/content/zh/docs/v3.3/application-store/external-apps/deploy-gitlab.md @@ -72,7 +72,7 @@ weight: 14310 1. 选择**配置** > **保密字典**,在搜索栏输入 `gitlab-initial-root-password`,然后按下键盘上的**回车键**来搜索密钥。 -2. 点击密钥访问其详情页,然后点击右上角的 查看密码。请确保将密码进行复制。 +2. 点击密钥访问其详情页,然后点击右上角的 icon 查看密码。请确保将密码进行复制。 ### 步骤 4:编辑 hosts 文件 diff --git a/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md b/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md index 0c61253a8..777e44ec9 100644 --- a/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md +++ b/content/zh/docs/v3.3/cluster-administration/cluster-settings/cluster-gateway.md @@ -62,7 +62,7 @@ KubeSphere v3.3.0 提供集群级别的网关,使所有项目共用一个全 3. 点击**监控**选项卡,查看集群网关的监控指标。 4. 点击**配置选项**选项卡以查看集群网关的配置选项。 5. 点击**网关日志**选项卡以查看集群网关日志。 -6. 点击**资源状态**选项卡,以查看集群网关的负载状态。点击 按钮,以增加或减少副本数量。 +6. 点击**资源状态**选项卡,以查看集群网关的负载状态。点击 iconicon 按钮,以增加或减少副本数量。 7. 点击**元数据**选项卡,以查看集群网关的注解。 ## 查看项目网关 diff --git a/content/zh/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md b/content/zh/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md index c4284ce05..c8003efb8 100644 --- a/content/zh/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md +++ b/content/zh/docs/v3.3/devops-user-guide/examples/use-nexus-in-pipelines.md @@ -44,7 +44,7 @@ weight: 11450 2. 在您的 **learn-pipline-java** GitHub 仓库中,点击根目录下的文件 `pom.xml`。 -3. 在文件中点击 以修改 `` 代码片段。设置 `` 并使用您的 Nexus 仓库的 URL。 +3. 在文件中点击 icon 以修改 `` 代码片段。设置 `` 并使用您的 Nexus 仓库的 URL。 ![modify-pom](/images/docs/v3.3/zh-cn/devops-user-guide/examples/use-nexus-in-pipeline/modify-pom.png) diff --git a/content/zh/docs/v3.3/project-administration/disk-log-collection.md b/content/zh/docs/v3.3/project-administration/disk-log-collection.md index 7b591ff0c..63578fba7 100644 --- a/content/zh/docs/v3.3/project-administration/disk-log-collection.md +++ b/content/zh/docs/v3.3/project-administration/disk-log-collection.md @@ -71,7 +71,7 @@ KubeSphere 支持多种日志收集方式,使运维团队能够以灵活统一 1. 在**部署**选项卡下,点击刚才创建的部署以访问其详情页。 -2. 在**资源状态**中,点击 查看容器详情,然后点击 `logsidecar-container`(filebeat 容器)日志图标 以检查日志。 +2. 在**资源状态**中,点击 查看容器详情,然后点击 `logsidecar-container`(filebeat 容器)日志图标 icon 以检查日志。 3. 或者,您也可以使用右下角**工具箱**中的**日志查询**功能来查看标准输出日志。例如,使用该部署的 Pod 名称进行模糊匹配。 diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md index 3b6e32e15..9bbd013ce 100644 --- a/content/zh/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md +++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/container-image-settings.md @@ -18,7 +18,7 @@ weight: 10280 ### 容器组副本数量 -点击 图标设置容器组副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。该选项对守护进程集不可用。 +点击 iconicon 图标设置容器组副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。该选项对守护进程集不可用。 如果您在多集群项目中创建部署,请在**副本调度模式**下选择一个副本调度模式: @@ -33,7 +33,7 @@ weight: 10280 #### 镜像搜索栏 -您可以点击右边的 ,从列表中选择一个镜像,或者输入镜像名称进行搜索。KubeSphere 提供 Docker Hub 的镜像以及您的私有镜像仓库的镜像。如果想使用私有镜像仓库,您需要先在**配置**下的**保密字典**中创建镜像仓库保密字典。 +您可以点击右边的 icon,从列表中选择一个镜像,或者输入镜像名称进行搜索。KubeSphere 提供 Docker Hub 的镜像以及您的私有镜像仓库的镜像。如果想使用私有镜像仓库,您需要先在**配置**下的**保密字典**中创建镜像仓库保密字典。 {{< notice note >}} diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/cronjobs.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/cronjobs.md index cc12744b1..fc1551fbb 100644 --- a/content/zh/docs/v3.3/project-user-guide/application-workloads/cronjobs.md +++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/cronjobs.md @@ -80,7 +80,7 @@ weight: 10260 3. 点击任意记录,您将转到该任务的详情页面。 -4. 在**资源状态**中,您可以检查容器组状态。点击右侧的 ,然后点击 可以检查容器日志,如下所示,该日志显示预期输出。 +4. 在**资源状态**中,您可以检查容器组状态。点击右侧的 icon,然后点击 icon 可以检查容器日志,如下所示,该日志显示预期输出。 ## 定时任务操作 diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md index a47cc0c59..0e4f43484 100644 --- a/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md +++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/deployments.md @@ -27,7 +27,7 @@ weight: 10210 ### 步骤 3:设置容器组 -1. 设置镜像前,请点击**容器组副本数量**中的 来定义容器组的副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。 +1. 设置镜像前,请点击**容器组副本数量**中的 iconicon 来定义容器组的副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。 {{< notice tip >}} 您可以启用右上角的**编辑 YAML**,查看 YAML 格式的部署清单文件。KubeSphere 使您可以直接编辑清单文件创建部署,或者您可以按照下列步骤使用仪表板创建部署。 @@ -104,7 +104,7 @@ weight: 10210 4. 点击**资源状态**选项卡,查看该部署的端口和容器组信息。 - - **副本运行状态**:点击 来增加或减少容器组副本数量。 + - **副本运行状态**:点击 iconicon 来增加或减少容器组副本数量。 - **容器组** - 容器组列表中显示了容器组详情(运行状态、节点、容器组 IP 以及资源使用情况)。 diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md index a0a780ba9..5d43bbe1b 100644 --- a/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md +++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/jobs.md @@ -115,7 +115,7 @@ weight: 10250 {{< notice tip >}}如果任务失败,您可以重新运行该任务,失败原因显示在**消息**下。{{}} -3. 在**资源状态**中,您可以查看容器组状态。先前将**并行容器组数量**设置为 2,因此每次会创建两个容器组。点击右侧的 ,然后点击 查看容器日志,该日志显示了预期的计算结果。 +3. 在**资源状态**中,您可以查看容器组状态。先前将**并行容器组数量**设置为 2,因此每次会创建两个容器组。点击右侧的 ,然后点击 icon 查看容器日志,该日志显示了预期的计算结果。 {{< notice tip >}} diff --git a/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md b/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md index 89f07cc32..690307978 100644 --- a/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md +++ b/content/zh/docs/v3.3/project-user-guide/application-workloads/statefulsets.md @@ -40,7 +40,7 @@ weight: 10220 ### 步骤 3:设置容器组 -1. 设置镜像前,请点击**容器组副本数量**中的 来定义容器组的副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。 +1. 设置镜像前,请点击**容器组副本数量**中的 iconicon 来定义容器组的副本数量,该参数显示在清单文件中的 `.spec.replicas` 字段。 {{< notice tip >}} @@ -113,7 +113,7 @@ weight: 10220 4. 点击**资源状态**选项卡,查看该有状态副本集的端口和容器组信息。 - - **副本运行状态**:点击 来增加或减少容器组副本数量。 + - **副本运行状态**:点击 iconicon 来增加或减少容器组副本数量。 - **容器组** - 容器组列表中显示了容器组详情(运行状态、节点、容器组IP 以及资源使用情况)。 diff --git a/content/zh/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md b/content/zh/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md index 4578d7d05..1e62377a5 100644 --- a/content/zh/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md +++ b/content/zh/docs/v3.3/project-user-guide/custom-application-monitoring/examples/monitor-sample-web.md @@ -61,7 +61,7 @@ weight: 10813 3. 在左上角输入标题(例如 `示例 Web 概览`)。 -4. 点击左列的 ,创建文本图表。 +4. 点击左列的 icon,创建文本图表。 5. 在**监控指标**字段输入 PromQL 表达式 `myapp_processed_ops_total`,并设置图表名称(例如 `操作数`)。点击右下角的 **√** 继续。 diff --git a/content/zh/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md b/content/zh/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md index b3aaf2260..d45d32432 100644 --- a/content/zh/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md +++ b/content/zh/docs/v3.3/quick-start/deploy-bookinfo-to-k8s.md @@ -53,7 +53,7 @@ Bookinfo 应用由以下四个独立的微服务组成,其中 **reviews** 微 {{< notice note >}} -KubeSphere 会自动创建主机名。若要更改主机名,请将鼠标悬停在默认路由规则上,然后点击 进行编辑。有关更多信息,请参见[创建基于微服务的应用](../../project-user-guide/application/compose-app/)。 +KubeSphere 会自动创建主机名。若要更改主机名,请将鼠标悬停在默认路由规则上,然后点击 icon 进行编辑。有关更多信息,请参见[创建基于微服务的应用](../../project-user-guide/application/compose-app/)。 {{}}