Merge pull request #3236 from zhuxiujuan28/docs

【documentation】add https doc & remove whizard and notification-history docs

Author: ks-ci-bot

content/en/docs/v4.1/02-quickstart/02-access-kubesphere-via-https.adoc

@@ -2,7 +2,7 @@
 title: "Install and Use Extensions"
 keywords: "Kubernetes, KubeSphere, quick start, install extensions, example, DevOps, extension features"
 description: "Introduce all extensions and demonstrate how to install them."
-weight: 02
+weight: 03
 ---
 
 

…-quickstart/02-install-an-extension.adoc …-quickstart/03-install-an-extension.adoccontent/en/docs/v4.1/02-quickstart/02-install-an-extension.adoc renamed to content/en/docs/v4.1/02-quickstart/03-install-an-extension.adoc content/en/docs/v4.1/02-quickstart/02-install-an-extension.adoc renamed to content/en/docs/v4.1/02-quickstart/03-install-an-extension.adoc

@@ -3,7 +3,7 @@ title: "Control User Permissions"
 linkTitle: "Create Workspaces, Projects, Users, and Roles"
 keywords: "Kubernetes, KubeSphere, Quick Start, User Permissions"
 description: "Learn how to create users and control their permissions by roles in workspaces and projects."
-weight: 03
+weight: 04
 ---
 
 ifeval::["{file_output_type}" == "html"]

…ckstart/03-control-user-permissions.adoc …ckstart/04-control-user-permissions.adoccontent/en/docs/v4.1/02-quickstart/03-control-user-permissions.adoc renamed to content/en/docs/v4.1/02-quickstart/04-control-user-permissions.adoc content/en/docs/v4.1/02-quickstart/03-control-user-permissions.adoc renamed to content/en/docs/v4.1/02-quickstart/04-control-user-permissions.adoc

@@ -22,7 +22,7 @@ image:/images/ks-qkcp/zh/v4.1/WordPress.png[]
 
 == Prerequisites
 
-* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../03-control-user-permissions/[Control User Permissions].
+* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../04-control-user-permissions/[Control User Permissions].
 
 * **KubeSphere Service Mesh** should have been installed and enabled.
 

content/en/docs/v4.1/02-quickstart/05-deploy-wordpress.adoc

@@ -33,7 +33,7 @@ image:/images/ks-qkcp/zh/v4.1/bookinfo.png[]
 
 == Prerequisites
 
-* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../03-control-user-permissions/[Control User Permissions].
+* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../04-control-user-permissions/[Control User Permissions].
 
 * **KubeSphere Service Mesh** and **KubeSphere Gateway** should have been installed and enabled.
 

content/en/docs/v4.1/02-quickstart/06-deploy-bookinfo.adoc

@@ -11,7 +11,7 @@ This method allows for efficient testing of performance and reliability, helping
 
 == Prerequisites
 
-* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../03-control-user-permissions/[Control User Permissions].
+* Prepare a project (e.g., **demo-project**) and a user (e.g., **project-regular**). The user should have been invited to the project and has the **operator** role in it. For more information, please refer to link:../04-control-user-permissions/[Control User Permissions].
 
 * **KubeSphere Service Mesh** and **KubeSphere Gateway** should have been installed and enabled.
 

content/en/docs/v4.1/02-quickstart/07-canary-release-example.adoc

@@ -9,7 +9,7 @@ This section demonstrates how to create and manage DevOps projects.
 
 == Prerequisites
 
-* A workspace and a user (**project-admin**) have been created. Invite this user to the workspace and assign them the **workspace-self-provisioner** role. For more information, see link:../../../../02-quickstart/03-control-user-permissions[Control User Permissions].
+* A workspace and a user (**project-admin**) have been created. Invite this user to the workspace and assign them the **workspace-self-provisioner** role. For more information, see link:../../../../02-quickstart/04-control-user-permissions[Control User Permissions].
 
 * **DevOps** must have been installed and enabled.
 

content/en/docs/v4.1/11-use-extensions/01-devops/03-how-to-use/01-devops-project-management.adoc

@@ -8,7 +8,7 @@ The WhizardTelemetry Platform Service is the common service for all extensions o
 
 **Configuration:**
 
-* Modify the extension configuration of WhizardTelemetry Platform Service in conjunction with WhizardTelemetry Monitoring to enable the Whizard Observability Center. For more information, see link:../../07-whizard/01-enable-whizard/[Whizard Observability Center].
+// * Modify the extension configuration of WhizardTelemetry Platform Service in conjunction with WhizardTelemetry Monitoring to enable the Whizard Observability Center. For more information, see link:../../07-whizard/01-enable-whizard/[Whizard Observability Center].
 
 * When configuring the OpenSearch log receivers for WhizardTelemetry Logging, WhizardTelemetry Auditing, WhizardTelemetry Events, and notification history, if you need to use multiple OpenSearch databases, configure them as follows.
 +
@@ -112,13 +112,3 @@ whizard-telemetry:
             username: admin
             password: admin
 ----
-
-
-// //note
-// [.admon.note,cols="a"]
-// |===
-// |说明
-
-// |
-// 修改 WhizardTelemetry 平台服务的扩展组件配置，可配合 WhizardTelemetry 监控扩展组件，启用 Whizard 可观测中心。有关更多信息，请参阅 link:../../07-whizard/01-enable-whizard/[Whizard 可观测中心]。
-// |===

content/en/docs/v4.1/11-use-extensions/05-observability-platform/01-platform-services/01-intro.adoc

@@ -10,7 +10,8 @@ This section introduces how to use the "WhizardTelemetry Monitoring" extension.
 
 WhizardTelemetry Monitoring is an extension that provides monitoring functions in the WhizardTelemetry Observability Platform, including the Whizard Observability Center. It provides multi-tenant perspective cloud-native resource monitoring capabilities, including real-time and historical data display of core monitoring metrics for objects such as multiple clusters, nodes, workloads, GPU, and K8s control planes.
 
-This section only introduces the monitoring functions in a single-cluster environment. For alerting functions in a single-cluster environment, see link:../06-alerting[WhizardTelemetry Alerting]. For monitoring and alerting functions in a multi-cluster environment, see link:../07-whizard[Whizard Observability Center].
+This section only introduces the monitoring functions in a single-cluster environment. For alerting functions in a single-cluster environment, see link:../06-alerting[WhizardTelemetry Alerting]. 
+// For monitoring and alerting functions in a multi-cluster environment, see link:../07-whizard[Whizard Observability Center].
 
 After installing the "WhizardTelemetry Monitoring" extension, the **Monitoring & Alerting** option will be displayed in the left navigation pane of the cluster and project, and services under application workloads in the cluster and project will support **Edit Monitoring Exporter**. The following pages will also display relevant monitoring metrics data:
 

content/en/docs/v4.1/11-use-extensions/05-observability-platform/05-monitoring/_index.adoc

@@ -16,7 +16,8 @@ After creating a rule group, the system can generate alerts when specific monito
 |Note
 
 |
-- {ks_product-en} provides built-in rule groups for clusters, and also supports custom rule groups. If the Whizard Observability Center is enabled, built-in rule groups can only be managed in the Whizard Observability Center. For more information, see link:../../07-whizard/05-alert-management/01-rule-groups/[Whizard Rule Groups].
+- {ks_product-en} provides built-in rule groups for clusters, and also supports custom rule groups. 
+// If the Whizard Observability Center is enabled, built-in rule groups can only be managed in the Whizard Observability Center. For more information, see link:../../07-whizard/05-alert-management/01-rule-groups/[Whizard Rule Groups].
 
 - In projects, only custom rule groups are supported.
 |===