From 1493577886a58f08493017c96b946aa00ab19204 Mon Sep 17 00:00:00 2001 From: Bettygogo2021 <91529409+Bettygogo2021@users.noreply.github.com> Date: Thu, 7 Jul 2022 19:58:57 +0800 Subject: [PATCH] fix 404-2 Signed-off-by: Bettygogo2021 <91529409+Bettygogo2021@users.noreply.github.com> --- .../v3.3/application-store/external-apps/deploy-litmus.md | 2 +- .../docs/v3.3/application-store/external-apps/deploy-tidb.md | 2 +- .../how-to-use/pipelines/gitlab-multibranch-pipeline.md | 2 +- .../en/docs/v3.3/installing-on-linux/introduction/intro.md | 2 +- content/en/docs/v3.3/introduction/what's-new-in-3.3.0.md | 2 +- .../en/docs/v3.3/multicluster-management/unbind-cluster.md | 2 +- content/zh/docs/v3.3/cluster-administration/storageclass.md | 4 +--- content/zh/docs/v3.3/introduction/what's-new-in-3.3.0.md | 2 +- 8 files changed, 8 insertions(+), 10 deletions(-) diff --git a/content/en/docs/v3.3/application-store/external-apps/deploy-litmus.md b/content/en/docs/v3.3/application-store/external-apps/deploy-litmus.md index fa32be68a..bd0b69c3c 100644 --- a/content/en/docs/v3.3/application-store/external-apps/deploy-litmus.md +++ b/content/en/docs/v3.3/application-store/external-apps/deploy-litmus.md @@ -24,7 +24,7 @@ This tutorial demonstrates how to deploy Litmus on KubeSphere and create chaos e ### Step 1: Add an app repository 1. In your workspace, go to **App Repositories** under **App Management**, and then click **Add**. -2. In the dialog that appears, set a name for the repository (for example, `litmus`) and enter the URL `https://litmuschaos.github.io/litmus-helm/`. Click **Validate** to verify the URL. You will see icon if the URL is available. Click **OK** to continue. +2. In the dialog that appears, set a name for the repository (for example, `litmus`) and enter the URL `https://litmuschaos.github.io/litmus-helm/`. Click **Validate** to verify the URL. Click **OK** to continue. 3. The app repository displays in the list after it is successfully imported. diff --git a/content/en/docs/v3.3/application-store/external-apps/deploy-tidb.md b/content/en/docs/v3.3/application-store/external-apps/deploy-tidb.md index 6ed44472d..b331b32a6 100644 --- a/content/en/docs/v3.3/application-store/external-apps/deploy-tidb.md +++ b/content/en/docs/v3.3/application-store/external-apps/deploy-tidb.md @@ -82,7 +82,7 @@ The process of deploying a TiDB cluster is similar to deploying TiDB Operator. 4. On the **Basic Information** page, confirm the app name, app version, and deployment location. Click **Next** to continue. -5. Some TiDB components require [persistent volumes](../../../cluster-administration/persistent-volume-and-storage-class/). You can run the following command to view your storage classes. +5. Some TiDB components require [storage classes](../../../cluster-administration/storageclass/). You can run the following command to view your storage classes. ``` $ kubectl get sc diff --git a/content/en/docs/v3.3/devops-user-guide/how-to-use/pipelines/gitlab-multibranch-pipeline.md b/content/en/docs/v3.3/devops-user-guide/how-to-use/pipelines/gitlab-multibranch-pipeline.md index fc2a3c775..3d4563fe9 100644 --- a/content/en/docs/v3.3/devops-user-guide/how-to-use/pipelines/gitlab-multibranch-pipeline.md +++ b/content/en/docs/v3.3/devops-user-guide/how-to-use/pipelines/gitlab-multibranch-pipeline.md @@ -77,7 +77,7 @@ You need to create two projects, such as `kubesphere-sample-dev` and `kubesphere If you want to use a private repository from GitLab, refer to the following steps: - Go to **User Settings > Access Tokens** on GitLab to create an access token with API and read_repository permissions. - - [Log in to the Jenkins dashboard](../../how-to-integrate/sonarqube/#step-5-add-the-sonarqube-server-to-jenkins), go to **Manage Jenkins > Manage Credentials** to use your GitLab token to create a Jenkins credential for accessing GitLab, and go to **Manage Jenkins > Configure System** to add the credential in **GitLab Server**. + - [Log in to the Jenkins dashboard](../../../how-to-integrate/sonarqube/#step-5-add-the-sonarqube-server-to-jenkins), go to **Manage Jenkins > Manage Credentials** to use your GitLab token to create a Jenkins credential for accessing GitLab, and go to **Manage Jenkins > Configure System** to add the credential in **GitLab Server**. - In your DevOps project, select **DevOps Project Settings > Credentials** to use your GitLab token to create a credential. You have to specify the credential for **Credential** on the **GitLab** tab when creating a pipeline so that the pipeline can pull code from your private GitLab repository. {{}} diff --git a/content/en/docs/v3.3/installing-on-linux/introduction/intro.md b/content/en/docs/v3.3/installing-on-linux/introduction/intro.md index ebf54824e..c34eebcb8 100644 --- a/content/en/docs/v3.3/installing-on-linux/introduction/intro.md +++ b/content/en/docs/v3.3/installing-on-linux/introduction/intro.md @@ -51,7 +51,7 @@ The quick installation of KubeSphere is only for development or testing since it KubeSphere allows you to configure persistent storage services both before and after installation. Meanwhile, KubeSphere supports a variety of open-source storage solutions (for example, Ceph and GlusterFS) as well as commercial storage products. Refer to [Persistent Storage Configurations](../../../installing-on-linux/persistent-storage-configurations/understand-persistent-storage/) for detailed instructions regarding how to configure the storage class before you install KubeSphere. -For more information about how to set different storage classes for your workloads after you install KubeSphere, see [Persistent Volumes and Storage Classes](../../../cluster-administration/persistent-volume-and-storage-class/). +For more information about how to set different storage classes for your workloads after you install KubeSphere, see [Storage Classes](../../../cluster-administration/storageclass/). ## Cluster Operation and Maintenance diff --git a/content/en/docs/v3.3/introduction/what's-new-in-3.3.0.md b/content/en/docs/v3.3/introduction/what's-new-in-3.3.0.md index 7bc38614e..14d4afd25 100644 --- a/content/en/docs/v3.3/introduction/what's-new-in-3.3.0.md +++ b/content/en/docs/v3.3/introduction/what's-new-in-3.3.0.md @@ -8,6 +8,6 @@ weight: 1400 In June 2022, KubeSphere 3.3.0 has been released with more exciting features. This release introduces GitOps-based continuous deployment and supports Git-based code repository management to further optimize the DevOps feature. Moreover, it also provides enhanced features of storage, multi-tenancy, multi-cluster, observability, app store, service mesh, and edge computing, to further perfect the interactive design for better user experience. -If you want to know details about new feature of KubeSphere 3.3.0, you can read the article [KubeSphere 3.3.0: Embrace GitOps](../news/kubesphere-3.3.0-ga-announcement/). +If you want to know details about new feature of KubeSphere 3.3.0, you can read the article [KubeSphere 3.3.0: Embrace GitOps](/../../news/kubesphere-3.3.0-ga-announcement/). In addition to the above highlights, this release also features other functionality upgrades and fixes the known bugs. There were some deprecated or removed features in 3.3.0. For more and detailed information, see the [Release Notes for 3.3.0](../../../v3.3/release/release-v330/). \ No newline at end of file diff --git a/content/en/docs/v3.3/multicluster-management/unbind-cluster.md b/content/en/docs/v3.3/multicluster-management/unbind-cluster.md index e8f5a7b46..e31f70506 100644 --- a/content/en/docs/v3.3/multicluster-management/unbind-cluster.md +++ b/content/en/docs/v3.3/multicluster-management/unbind-cluster.md @@ -20,7 +20,7 @@ You can unbind a cluster by using either of the following methods: 1. Click **Platform** in the upper-left corner and select **Cluster Management**. -2. In the **Member Clusters** area, click on the right of the the cluster that you want to remove from the control plane, and then click **Unbind Cluster**. +2. In the **Member Clusters** area, click on the right of the the cluster that you want to remove from the control plane, and then click **Unbind Cluster**. 3. In the **Unbind Cluster** dialog box that is displayed, read the risk alert carefully. If you still want to proceed, enter the name of the member cluster, and click **OK**. diff --git a/content/zh/docs/v3.3/cluster-administration/storageclass.md b/content/zh/docs/v3.3/cluster-administration/storageclass.md index 1fd0830aa..e14a0941c 100644 --- a/content/zh/docs/v3.3/cluster-administration/storageclass.md +++ b/content/zh/docs/v3.3/cluster-administration/storageclass.md @@ -184,9 +184,7 @@ NFS（网络文件系统）广泛用于带有 [NFS-Client](https://github.com/ku ## 管理存储类 -创建存储类型后，点击此存储类型的名称前往其详情页。在详情页点击**编辑 YAML** 来编辑此存储类型的清单文件。关于参数解释，您可以参考[设置存储类](../../cluster-administration/persistent-volume-and-storage-class/#设置存储类)。同时，您也可以参考 Kubernetes 官方文档的[参数](https://kubernetes.io/zh/docs/concepts/storage/storage-classes/#参数)部分。 - -同时，您也可以点击**更多操作**并在下拉菜单中选择一项操作： +创建存储类型后，点击此存储类型的名称前往其详情页。在详情页点击**编辑 YAML** 来编辑此存储类型的清单文件。您也可以点击**更多操作**并在下拉菜单中选择一项操作： - **设为默认存储类**：将此存储类设为集群的默认存储类。一个 KubeSphere 集群中仅允许设置一个默认存储类。 - **设置授权规则**：只允许特定项目和企业空间使用该存储类。 diff --git a/content/zh/docs/v3.3/introduction/what's-new-in-3.3.0.md b/content/zh/docs/v3.3/introduction/what's-new-in-3.3.0.md index 6577c74e5..15d51d346 100644 --- a/content/zh/docs/v3.3/introduction/what's-new-in-3.3.0.md +++ b/content/zh/docs/v3.3/introduction/what's-new-in-3.3.0.md @@ -8,6 +8,6 @@ weight: 1400 2022 年 6 月 24 日，KubeSphere 3.3.0 正式发布，带来了更多令人期待的功能。新增了基于 GitOps 的持续部署方案，进一步优化了 DevOps 的使用体验。同时还增强了 “多集群管理、多租户管理、可观测性、应用商店、微服务治理、边缘计算、存储” 等特性，更进一步完善交互设计，并全面提升了用户体验。 -关于 3.3.0 新特性的详细解读，可参考博客 [KubeSphere 3.3.0 发布：全面拥抱 GitOps](/zh/news/kubesphere-3.3.0-ga-announcement/)。 +关于 3.3.0 新特性的详细解读，可参考博客 [KubeSphere 3.3.0 发布：全面拥抱 GitOps](/../../news/kubesphere-3.3.0-ga-announcement/)。 关于 3.3.0 的新功能及增强、Bug 修复、重要的技术调整，以及废弃或移除的功能，请参见 [3.3.0 版本说明](../../../v3.3/release/release-v330/)。 \ No newline at end of file