diff --git a/content/en/docs/pluggable-components/alerting.md b/content/en/docs/pluggable-components/alerting.md index 0f0c7f156..e8e242eff 100644 --- a/content/en/docs/pluggable-components/alerting.md +++ b/content/en/docs/pluggable-components/alerting.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere Alerting" weight: 6600 --- -## What is KubeSphere Alerting - Alerting is an important building block of observability, closely related to monitoring and logging. The alerting system in KubeSphere, coupled with the proactive failure notification system, allows users to know activities of interest based on alerting policies. When a predefined threshold of a certain metric is reached, an alert will be sent to preconfigured recipients. Therefore, you need to configure the notification method beforehand, including Email, Slack, DingTalk, WeCom and Webhook. With a highly functional alerting and notification system in place, you can quickly identify and resolve potential issues in advance before they affect your business. ## Enable Alerting before Installation @@ -60,7 +58,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -74,7 +72,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `alerting` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -89,8 +87,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/app-store.md b/content/en/docs/pluggable-components/app-store.md index 4ba3750df..5af359e33 100644 --- a/content/en/docs/pluggable-components/app-store.md +++ b/content/en/docs/pluggable-components/app-store.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere App Store" weight: 6200 --- -## What is KubeSphere App Store - As an open-source and app-centric container platform, KubeSphere provides users with a Helm-based App Store for application lifecycle management on the back of [OpenPitrix](https://github.com/openpitrix/openpitrix), an open-source web-based system to package, deploy and manage different types of apps. The KubeSphere App Store allows ISVs, developers and users to upload, test, deploy and release apps with just several clicks in a one-stop shop. Internally, the KubeSphere App Store can serve as a place for different teams to share data, middleware, and office applications. Externally, it is conducive to setting industry standards of building and delivery. By default, there are 16 built-in apps in the App Store. After you enable this feature, you can add more apps with app templates. @@ -68,7 +66,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -76,8 +74,6 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-app-store/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} @@ -86,9 +82,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-app-store/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `openpitrix` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -104,10 +98,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} - + {{< notice note >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} diff --git a/content/en/docs/pluggable-components/auditing-logs.md b/content/en/docs/pluggable-components/auditing-logs.md index a1a262533..b0a0382bf 100644 --- a/content/en/docs/pluggable-components/auditing-logs.md +++ b/content/en/docs/pluggable-components/auditing-logs.md @@ -6,9 +6,7 @@ linkTitle: "KubeSphere Auditing Logs" weight: 6700 --- -## What are KubeSphere Auditing Logs - -KubeSphere Auditing Log System provides a security-relevant chronological set of records documenting the sequence of activities related to individual users, managers, or other components of the system. Each request to KubeSphere generates an event that is then written to a webhook and processed according to a certain rule. +The KubeSphere Auditing Log System provides a security-relevant chronological set of records documenting the sequence of activities related to individual users, managers, or other components of the system. Each request to KubeSphere generates an event that is then written to a webhook and processed according to a certain rule. For more information, see [Auditing Log Query](../../toolbox/auditing/auditing-query/). @@ -94,7 +92,7 @@ By default, ks-installer will install Elasticsearch internally if Auditing is en ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -102,17 +100,13 @@ By default, ks-installer will install Elasticsearch internally if Auditing is en 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `auditing` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -143,8 +137,9 @@ By default, Elasticsearch will be installed internally if Auditing is enabled. F kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/devops.md b/content/en/docs/pluggable-components/devops.md index a2a8543d7..bee829c69 100644 --- a/content/en/docs/pluggable-components/devops.md +++ b/content/en/docs/pluggable-components/devops.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere DevOps System" weight: 6300 --- -## What is KubeSphere DevOps System - The KubeSphere DevOps System is designed for CI/CD workflows in Kubernetes. Based on [Jenkins](https://jenkins.io/), it provides one-stop solutions to help both development and Ops teams build, test and publish apps to Kubernetes in a straight-forward way. It also features plugin management, [Binary-to-Image (B2I)](../../project-user-guide/image-builder/binary-to-image/), [Source-to-Image (S2I)](../../project-user-guide/image-builder/source-to-image/), code dependency caching, code quality analysis, pipeline logging, etc. The DevOps System offers an enabling environment for users as apps can be automatically released to the same platform. It is also compatible with third-party private image registries (e.g. Harbor) and code repositories (e.g. GitLab/GitHub/SVN/BitBucket). As such, it creates excellent user experiences by providing users with comprehensive, visualized CI/CD pipelines which are extremely useful in air-gapped environments. @@ -64,7 +62,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -72,8 +70,6 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-devops-system/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} @@ -82,9 +78,8 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-devops-system/edit-yaml.png) 4. In this YAML file, navigate to `devops` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. ```yaml @@ -98,9 +93,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} + {{< notice note >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} diff --git a/content/en/docs/pluggable-components/events.md b/content/en/docs/pluggable-components/events.md index 534d39c87..fb7497ccd 100644 --- a/content/en/docs/pluggable-components/events.md +++ b/content/en/docs/pluggable-components/events.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere Events" weight: 6500 --- -## What are KubeSphere Events - KubeSphere events allow users to keep track of what is happening inside a cluster, such as node scheduling status and image pulling result. They will be accurately recorded with the specific reason, status and message displayed in the web console. To query events, users can quickly launch the web Toolkit and enter related information in the search bar with different filters (e.g keyword and project) available. Events can also be archived to third-party tools, such as Elasticsearch, Kafka or Fluentd. For more information, see [Event Query](../../toolbox/events-query/). @@ -96,7 +94,7 @@ By default, ks-installer will install Elasticsearch internally if Events is enab ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -104,8 +102,6 @@ By default, ks-installer will install Elasticsearch internally if Events is enab 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-events/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} @@ -114,9 +110,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-events/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `events` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -148,9 +142,9 @@ By default, Elasticsearch will be installed internally if Events is enabled. For kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} + {{< notice note >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} diff --git a/content/en/docs/pluggable-components/kubeedge.md b/content/en/docs/pluggable-components/kubeedge.md index 4103b006f..3b76f68e9 100644 --- a/content/en/docs/pluggable-components/kubeedge.md +++ b/content/en/docs/pluggable-components/kubeedge.md @@ -6,8 +6,6 @@ linkTitle: "KubeEdge" weight: 6930 --- -## What is KubeEdge - [KubeEdge](https://kubeedge.io/en/) is an open-source system for extending native containerized application orchestration capabilities to hosts at edge. It supports multiple edge protocols and looks to provide unified management of cloud and edge applications and resources. KubeEdge has components running in two separate places - cloud and edge nodes. The components running on the cloud, collectively known as CloudCore, include Controllers and Cloud Hub. Cloud Hub serves as the gateway for the requests sent by edge nodes while Controllers function as orchestrators. The components running on edge nodes, collectively known as EdgeCore, include EdgeHub, EdgeMesh, MetadataManager, and DeviceTwin. For more information, see [the KubeEdge website](https://kubeedge.io/en/). @@ -84,7 +82,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `kubeedge.enabled` and enable it by setting it to `true`. @@ -107,8 +105,9 @@ The `kubeedge` section is not included in `cluster-configuration.yaml` if your c kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Enable KubeEdge after Upgrade diff --git a/content/en/docs/pluggable-components/logging.md b/content/en/docs/pluggable-components/logging.md index 0a845f49b..fa0fa3666 100644 --- a/content/en/docs/pluggable-components/logging.md +++ b/content/en/docs/pluggable-components/logging.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere Logging System" weight: 6400 --- -## What is KubeSphere Logging System - KubeSphere provides a powerful, holistic and easy-to-use logging system for log collection, query and management. It covers logs at varied levels, including tenants, infrastructure resources, and applications. Users can search logs from different dimensions, such as project, workload, Pod and keyword. Compared with Kibana, the tenant-based logging system of KubeSphere features better isolation and security among tenants as tenants can only view their own logs. Apart from KubeSphere's own logging system, the container platform also allows users to add third-party log collectors, such as Elasticsearch, Kafka and Fluentd. For more information, see [Log Query](../../toolbox/log-query/). @@ -98,7 +96,7 @@ By default, ks-installer will install Elasticsearch internally if Logging is ena ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -106,8 +104,6 @@ By default, ks-installer will install Elasticsearch internally if Logging is ena 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-logging-system/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} @@ -116,9 +112,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-logging-system/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `logging` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -149,9 +143,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} + {{< notice note >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} diff --git a/content/en/docs/pluggable-components/metrics-server.md b/content/en/docs/pluggable-components/metrics-server.md index 06632cafd..09d38e014 100644 --- a/content/en/docs/pluggable-components/metrics-server.md +++ b/content/en/docs/pluggable-components/metrics-server.md @@ -6,8 +6,6 @@ linkTitle: "Metrics Server" weight: 6910 --- -## What is Metrics Server - KubeSphere supports Horizontal Pod Autoscalers (HPA) for [Deployments](../../project-user-guide/application-workloads/deployments/). In KubeSphere, the Metrics Server controls whether the HPA is enabled. You use an HPA object to autoscale a Deployment based on different types of metrics, such as CPU and memory utilization, as well as the minimum and maximum number of replicas. In this way, an HPA helps to make sure your application runs smoothly and consistently in different situations. ## Enable the Metrics Server before Installation @@ -60,12 +58,11 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` {{< notice note >}} - If you install KubeSphere on some cloud hosted Kubernetes engines, it is probable that the Metrics Server is already installed in your environment. In this case, it is not recommended that you enable it in `cluster-configuration.yaml` as it may cause conflicts during installation. {{}} @@ -74,17 +71,13 @@ If you install KubeSphere on some cloud hosted Kubernetes engines, it is probabl 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/metrics-server/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/metrics-server/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `metrics_server` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -99,8 +92,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/network-policy.md b/content/en/docs/pluggable-components/network-policy.md index 885940fbc..c15353092 100644 --- a/content/en/docs/pluggable-components/network-policy.md +++ b/content/en/docs/pluggable-components/network-policy.md @@ -6,8 +6,6 @@ linkTitle: "Network Policies" weight: 6900 --- -## What are Network Policies - Starting from v3.0.0, users can configure network policies of native Kubernetes in KubeSphere. Network Policies are an application-centric construct, enabling you to specify how a Pod is allowed to communicate with various network entities over the network. With network policies, users can achieve network isolation within the same cluster, which means firewalls can be set up between certain instances (Pods). {{< notice note >}} @@ -71,7 +69,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -79,17 +77,13 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/network-policies/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - - ![edit-yaml](/images/docs/enable-pluggable-components/network-policies/edit-yaml.png) +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `network.networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -105,8 +99,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/pod-ip-pools.md b/content/en/docs/pluggable-components/pod-ip-pools.md index 9e6281e8f..917b578c8 100644 --- a/content/en/docs/pluggable-components/pod-ip-pools.md +++ b/content/en/docs/pluggable-components/pod-ip-pools.md @@ -6,8 +6,6 @@ linkTitle: "Pod IP Pools" weight: 6920 --- -## What are Pod IP Pools - A Pod IP Pool is used to manage the Pod network address space, and the address space between each Pod IP Pool cannot overlap. When you create a workload, you can select a specific Pod IP Pool, so that created Pods will be assigned IP addresses from this Pod IP Pool. ## Enable Pod IP Pools before Installation @@ -77,7 +75,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `network` and change `network.ippool.type` to `calico`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -93,8 +91,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/service-mesh.md b/content/en/docs/pluggable-components/service-mesh.md index 9bab22a2f..aebae6466 100644 --- a/content/en/docs/pluggable-components/service-mesh.md +++ b/content/en/docs/pluggable-components/service-mesh.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere Service Mesh" weight: 6800 --- -## What is KubeSphere Service Mesh - On the basis of [Istio](https://istio.io/), KubeSphere Service Mesh visualizes microservices governance and traffic management. It features a powerful toolkit including **circuit breaking, blue-green deployment, canary release, traffic mirroring, distributed tracing, observability and traffic control**. Developers can easily get started with KubeSphere Service Mesh without any code hacking, with the learning curve of Istio greatly reduced. All features of KubeSphere Service Mesh are designed to meet users' demand for their business. For more information, see [Grayscale Release](../../project-user-guide/grayscale-release/overview/). @@ -62,7 +60,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -70,17 +68,14 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu 1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. - ![clusters-management](/images/docs/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png) - 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. {{< notice info >}} A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. - ![edit-yaml](/images/docs/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.png) - +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. + 4. In this YAML file, navigate to `servicemesh` and change `false` to `true` for `enabled`. After you finish, click **Update** in the bottom-right corner to save the configuration. ```yaml @@ -94,8 +89,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/en/docs/pluggable-components/service-topology.md b/content/en/docs/pluggable-components/service-topology.md index 6fa0ef533..25c1255cd 100644 --- a/content/en/docs/pluggable-components/service-topology.md +++ b/content/en/docs/pluggable-components/service-topology.md @@ -6,8 +6,6 @@ linkTitle: "Service Topology" weight: 6915 --- -## What is Service Topology - You can enable Service Topology to integrate [Weave Scope](https://www.weave.works/oss/scope/), a visualization and monitoring tool for Docker and Kubernetes. Weave Scope uses established APIs to collect information to build a topology of your apps and containers. The Service topology displays in your project, providing you with visual representations of connections based on traffic. ## Enable Service Topology before Installation @@ -77,7 +75,7 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects. {{}} -3. In **Resource List**, click the three dots on the right of `ks-installer` and select **Edit YAML**. +3. In **Resource List**, click on the right of `ks-installer` and select **Edit YAML**. 4. In this YAML file, navigate to `network` and change `network.topology.type` to `weave-scope`. After you finish, click **Update** in the bottom-right corner to save the configuration. @@ -93,8 +91,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -You can find the web kubectl tool by clicking the hammer icon in the bottom-right corner of the console. + {{< notice note >}} + +You can find the web kubectl tool by clicking in the bottom-right corner of the console. {{}} ## Verify the Installation of the Component diff --git a/content/zh/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md b/content/zh/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md index 1ddb343aa..87753ce61 100644 --- a/content/zh/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md +++ b/content/zh/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md @@ -104,7 +104,7 @@ kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3 {{< notice warning >}} -在开启 Istio 组件之前，由于自定义资源定义（CRD）冲突的问题，需要先删除华为 CCE 自带的 `applications.app.k8s.io` ，最直接的方式是通过 kubectl 工具来完成： +在开启 Istio 组件之前，由于自定义资源定义 (CRD) 冲突的问题，需要先删除华为 CCE 自带的 `applications.app.k8s.io` ，最直接的方式是通过 kubectl 工具来完成： ```bash kubectl delete crd applications.app.k8s.io diff --git a/content/zh/docs/pluggable-components/alerting.md b/content/zh/docs/pluggable-components/alerting.md index 4584ae115..82911f533 100644 --- a/content/zh/docs/pluggable-components/alerting.md +++ b/content/zh/docs/pluggable-components/alerting.md @@ -6,9 +6,7 @@ linkTitle: "KubeSphere 告警系统" weight: 6600 --- -## 什么是 KubeSphere 告警系统 - -告警是可观测性的重要构件，与监控和日志密切相关。KubeSphere 中的告警系统与其主动式故障通知 (Proactive Failure Notification) 系统相结合，使用户可以基于告警策略了解感兴趣的活动。当达到某个指标的预定义阈值时，会向预先配置的收件人发出告警。因此，您需要预先配置通知方式，包括邮件、Slack、钉钉、企业微信和 Webhook。有了功能强大的告警和通知系统，您就可以迅速发现并提前解决潜在问题，避免您的业务受影响。 +告警是可观测性的重要组成部分，与监控和日志密切相关。KubeSphere 中的告警系统与其主动式故障通知 (Proactive Failure Notification) 系统相结合，使用户可以基于告警策略了解感兴趣的活动。当达到某个指标的预定义阈值时，会向预先配置的收件人发出告警。因此，您需要预先配置通知方式，包括邮件、Slack、钉钉、企业微信和 Webhook。有了功能强大的告警和通知系统，您就可以迅速发现并提前解决潜在问题，避免您的业务受影响。 ## 在安装前启用告警系统 @@ -60,7 +58,7 @@ weight: 6600 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -68,17 +66,13 @@ weight: 6600 1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![cluster-management1](/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/cluster-management1.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 {{< notice info >}} 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![edit-yaml1](/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml1.png) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `alerting`，将 `enabled` 的 `false` 更改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -93,12 +87,13 @@ weight: 6600 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 如果您在**集群管理**页面可以看到**告警消息**和**告警策略**，说明安装成功，因为安装组件之后才会显示这两部分。 -![alerting1](/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting1.png) \ No newline at end of file +![alerting-section](/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/alerting-section.png) \ No newline at end of file diff --git a/content/zh/docs/pluggable-components/app-store.md b/content/zh/docs/pluggable-components/app-store.md index 8194407fa..b5e3c58e4 100644 --- a/content/zh/docs/pluggable-components/app-store.md +++ b/content/zh/docs/pluggable-components/app-store.md @@ -2,13 +2,10 @@ title: "KubeSphere 应用商店" keywords: "Kubernetes, KubeSphere, app-store, OpenPitrix" description: "了解如何启用应用商店，一个可以在内部实现数据和应用共享、并制定应用交付流程的行业标准的组件。" - linkTitle: "KubeSphere 应用商店" weight: 6200 --- -## 什么是 KubeSphere 应用商店 - 作为一个开源的、以应用为中心的容器平台，KubeSphere 在 [OpenPitrix](https://github.com/openpitrix/openpitrix) 的基础上，为用户提供了一个基于 Helm 的应用商店，用于应用生命周期管理。OpenPitrix 是一个开源的 Web 平台，用于打包、部署和管理不同类型的应用。KubeSphere 应用商店让 ISV、开发者和用户能够在一站式服务中只需点击几下就可以上传、测试、部署和发布应用。 对内，KubeSphere 应用商店可以作为不同团队共享数据、中间件和办公应用的场所。对外，有利于设立构建和交付的行业标准。默认情况下，应用商店中内置了 16 个应用。启用该功能后，您可以通过应用模板添加更多应用。 @@ -69,7 +66,7 @@ weight: 6200 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -77,17 +74,13 @@ weight: 6200 1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击结果查看其详细页面。 {{< notice info >}} 自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑配置文件](/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `openpitrix`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -103,8 +96,9 @@ weight: 6200 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/auditing-logs.md b/content/zh/docs/pluggable-components/auditing-logs.md index 763184c1a..5dfb6c9c9 100644 --- a/content/zh/docs/pluggable-components/auditing-logs.md +++ b/content/zh/docs/pluggable-components/auditing-logs.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere 审计日志" weight: 6700 --- -## 什么是 KubeSphere 审计日志 - KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排列的记录，按顺序记录了与单个用户、管理人员或系统其他组件相关的活动。对 KubeSphere 的每个请求都会生成一个事件，然后写入 Webhook，并根据一定的规则进行处理。 有关更多信息，请参见[审计日志查询](../../toolbox/auditing/auditing-query/)。 @@ -94,7 +92,7 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -102,17 +100,13 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。 {{< notice info >}} 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `auditing`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -143,8 +137,9 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/devops.md b/content/zh/docs/pluggable-components/devops.md index 47d73ddeb..74ba26400 100644 --- a/content/zh/docs/pluggable-components/devops.md +++ b/content/zh/docs/pluggable-components/devops.md @@ -2,13 +2,10 @@ title: "KubeSphere DevOps 系统" keywords: "Kubernetes, Jenkins, KubeSphere, DevOps, cicd" description: "了解如何启用 DevOps 系统来进一步解放您的开发人员，让他们专注于代码编写。" - linkTitle: "KubeSphere DevOps" weight: 6300 --- -## 什么是 KubeSphere DevOps 系统 - 基于 [Jenkins](https://jenkins.io/) 的 KubeSphere DevOps 系统是专为 Kubernetes 中的 CI/CD 工作流设计的，它提供了一站式的解决方案，帮助开发和运维团队用非常简单的方式构建、测试和发布应用到 Kubernetes。它还具有插件管理、[Binary-to-Image (B2I)](../../project-user-guide/image-builder/binary-to-image/)、[Source-to-Image (S2I)](../../project-user-guide/image-builder/source-to-image/)、代码依赖缓存、代码质量分析、流水线日志等功能。 DevOps 系统为用户提供了一个自动化的环境，应用可以自动发布到同一个平台。它还兼容第三方私有镜像仓库（如 Harbor）和代码库（如 GitLab/GitHub/SVN/BitBucket）。它为用户提供了全面的、可视化的 CI/CD 流水线，打造了极佳的用户体验，而且这种兼容性强的流水线能力在离线环境中非常有用。 @@ -65,7 +62,7 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -73,17 +70,13 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发 1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。 {{< notice info >}} -自定义资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 +自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `devops`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -98,8 +91,9 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/events.md b/content/zh/docs/pluggable-components/events.md index a8afa7e32..2d18b5b3a 100644 --- a/content/zh/docs/pluggable-components/events.md +++ b/content/zh/docs/pluggable-components/events.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere 事件系统" weight: 6500 --- -## 什么是 KubeSphere 事件系统 - KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如节点调度状态和镜像拉取结果。这些事件会被准确记录下来，并在 Web 控制台中显示具体的原因、状态和信息。要查询事件，用户可以快速启动 Web 工具箱，在搜索栏中输入相关信息，并有不同的过滤器（如关键字和项目）可供选择。事件也可以归档到第三方工具，例如 Elasticsearch、Kafka 或 Fluentd。 有关更多信息，请参见[事件查询](../../toolbox/events-query/)。 @@ -96,7 +94,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -104,8 +102,6 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 {{< notice info >}} @@ -114,9 +110,7 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `events`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -148,9 +142,9 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} + {{< notice note >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} diff --git a/content/zh/docs/pluggable-components/kubeedge.md b/content/zh/docs/pluggable-components/kubeedge.md index 72b8698cb..9d1ef4537 100644 --- a/content/zh/docs/pluggable-components/kubeedge.md +++ b/content/zh/docs/pluggable-components/kubeedge.md @@ -6,8 +6,6 @@ linkTitle: "KubeEdge" weight: 6930 --- -## 什么是 KubeEdge - [KubeEdge](https://kubeedge.io/zh/) 是一个开源系统，用于将容器化应用程序编排功能扩展到边缘的主机。KubeEdge 支持多个边缘协议，旨在对部署于云端和边端的应用程序与资源等进行统一管理。 KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上。在云上运行的组件统称为 CloudCore，包括 Controller 和 Cloud Hub。Cloud Hub 作为接收边缘节点发送请求的网关，Controller 则作为编排器。在边缘节点上运行的组件统称为 EdgeCore，包括 EdgeHub，EdgeMesh，MetadataManager 和 DeviceTwin。有关更多信息，请参见 [KubeEdge 网站](https://kubeedge.io/zh/)。 @@ -85,7 +83,7 @@ KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑配置文件**。 +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，然后选择**编辑配置文件**。 4. 在该配置文件中，搜寻到 `kubeedge.enabled`，将 `false` 更改为 `true` 以启用 KubeEdge。 @@ -108,8 +106,9 @@ KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标来找到 Web kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 来找到 Web kubectl 工具。 {{}} ## 在升级后启用 KubeEdge diff --git a/content/zh/docs/pluggable-components/logging.md b/content/zh/docs/pluggable-components/logging.md index d74333309..68188bc42 100644 --- a/content/zh/docs/pluggable-components/logging.md +++ b/content/zh/docs/pluggable-components/logging.md @@ -6,8 +6,6 @@ linkTitle: "KubeSphere 日志系统" weight: 6400 --- -## 什么是 KubeSphere 日志系统 - KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的、易于使用的日志系统。它涵盖了不同层级的日志，包括租户、基础设施资源和应用。用户可以从项目、工作负载、Pod 和关键字等不同维度对日志进行搜索。与 Kibana 相比，KubeSphere 基于租户的日志系统中，每个租户只能查看自己的日志，从而可以在租户之间提供更好的隔离性和安全性。除了 KubeSphere 自身的日志系统，该容器平台还允许用户添加第三方日志收集器，如 Elasticsearch、Kafka 和 Fluentd。 有关更多信息，请参见[日志查询](../../toolbox/log-query/)。 @@ -98,7 +96,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -106,19 +104,15 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 {{< notice info >}} -自定义资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 +自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑 yaml](/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `logging`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -149,9 +143,9 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} + {{< notice note >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} diff --git a/content/zh/docs/pluggable-components/metrics-server.md b/content/zh/docs/pluggable-components/metrics-server.md index fff1d23e1..515f925ee 100644 --- a/content/zh/docs/pluggable-components/metrics-server.md +++ b/content/zh/docs/pluggable-components/metrics-server.md @@ -6,8 +6,6 @@ linkTitle: "Metrics Server" weight: 6910 --- -## 什么是 Metrics Server - KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/deployments/)的 Pod 弹性伸缩程序 (HPA)。在 KubeSphere 中，Metrics Server 控制着 HPA 是否启用。您可以根据不同类型的指标（例如 CPU 和内存使用率，以及最小和最大副本数），使用 HPA 对象对部署 (Deployment) 自动伸缩。通过这种方式，HPA 可以帮助确保您的应用程序在不同情况下都能平稳、一致地运行。 ## 在安装前启用 Metrics Server @@ -60,12 +58,11 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` {{< notice note >}} - 如果您在某些云托管的 Kubernetes 引擎上安装 KubeSphere，那么很可能您的环境中已经安装了 Metrics Server。在这种情况下，不建议您在 `cluster-configuration.yaml` 中启用 Metrics Server，因为这可能会在安装过程中引起冲突。 {{}} @@ -73,8 +70,6 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d 1. 以 `admin` 身份登录控制台。点击左上角**平台管理**，选择**集群管理**。 - ![clusters-management](/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看详情页。 {{< notice info >}} @@ -83,9 +78,7 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d {{}} -3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，选择**编辑配置文件**。 - - ![edit-yaml](/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/edit-yaml.png) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，导航到 `metrics_server`，在 `enabled` 一行将 `false` 更改为 `true`。完成后，点击右下角的**更新**以保存配置。 @@ -100,8 +93,9 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -可以通过点击控制台右下角的锤子图标找到 kubectl 工具。 + {{< notice note >}} + +可以通过点击控制台右下角的 找到 kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/network-policy.md b/content/zh/docs/pluggable-components/network-policy.md index 8984ad606..297612bb6 100644 --- a/content/zh/docs/pluggable-components/network-policy.md +++ b/content/zh/docs/pluggable-components/network-policy.md @@ -6,8 +6,6 @@ linkTitle: "网络策略" weight: 6900 --- -## 什么是网络策略 - 从 3.0.0 版本开始，用户可以在 KubeSphere 中配置原生 Kubernetes 的网络策略。网络策略是一种以应用为中心的结构，使您能够指定如何允许 Pod 通过网络与各种网络实体进行通信。通过网络策略，用户可以在同一集群内实现网络隔离，这意味着可以在某些实例 (Pod) 之间设置防火墙。 {{< notice note >}} @@ -71,7 +69,7 @@ weight: 6900 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -79,17 +77,13 @@ weight: 6900 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/network-policies/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 {{< notice info >}} 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - - ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/network-policies/edit-yaml.PNG) +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 4. 在该 YAML 文件中，搜寻到 `network.networkpolicy`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 @@ -105,8 +99,9 @@ weight: 6900 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/pod-ip-pools.md b/content/zh/docs/pluggable-components/pod-ip-pools.md index 752418d2b..8375beeeb 100644 --- a/content/zh/docs/pluggable-components/pod-ip-pools.md +++ b/content/zh/docs/pluggable-components/pod-ip-pools.md @@ -6,8 +6,6 @@ linkTitle: "容器组 IP 池" weight: 6920 --- -## 什么是容器组 IP 池 - 容器组 IP 池用于规划 Pod 网络地址空间，每个容器组 IP 池之间的地址空间不能重叠。创建工作负载时，可选择特定的容器组 IP 池，这样创建出的 Pod 将从该容器组 IP 池中分配 IP。 ## 安装前启用容器组 IP 池 @@ -78,7 +76,7 @@ weight: 6920 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑配置文件**。 +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，然后选择**编辑配置文件**。 4. 在该配置文件中，搜寻到 `network`，将 `network.ippool.type` 更改为 `calico`。完成后，点击右下角的**更新**保存配置。 @@ -94,8 +92,9 @@ weight: 6920 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标来找到 Web kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 来找到 Web kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/service-mesh.md b/content/zh/docs/pluggable-components/service-mesh.md index b46d02737..1195c3cc2 100644 --- a/content/zh/docs/pluggable-components/service-mesh.md +++ b/content/zh/docs/pluggable-components/service-mesh.md @@ -2,13 +2,10 @@ title: "KubeSphere 服务网格" keywords: "Kubernetes, Istio, KubeSphere, 服务网格, 微服务" description: "了解如何启用服务网格，从而提供不同的流量管理策略进行微服务治理。" - linkTitle: "KubeSphere 服务网格" weight: 6800 --- -## 什么是 KubeSphere 服务网格 - KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和流量管理可视化。它拥有强大的工具包，包括**熔断机制、蓝绿部署、金丝雀发布、流量镜像、分布式链路追踪、可观测性和流量控制**等。KubeSphere 服务网格支持代码无侵入的微服务治理，帮助开发者快速上手，Istio 的学习曲线也极大降低。KubeSphere 服务网格的所有功能都旨在满足用户的业务需求。 有关更多信息，请参见[灰度发布](../../project-user-guide/grayscale-release/overview/)。 @@ -63,7 +60,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和 ```bash kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.1.0/kubesphere-installer.yaml - + kubectl apply -f cluster-configuration.yaml ``` @@ -71,17 +68,14 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 - ![集群管理](/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png) - 2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 {{< notice info >}} 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右边的三个点，选择**编辑配置文件**。 - ![编辑 YAML](/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.PNG) - +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，选择**编辑配置文件**。 + 4. 在该 YAML 文件中，搜寻到 `servicemesh`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 ```yaml @@ -95,8 +89,9 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标找到 Web Kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 找到 Web Kubectl 工具。 {{}} ## 验证组件的安装 diff --git a/content/zh/docs/pluggable-components/service-topology.md b/content/zh/docs/pluggable-components/service-topology.md index 872f91f74..7dae1a32f 100644 --- a/content/zh/docs/pluggable-components/service-topology.md +++ b/content/zh/docs/pluggable-components/service-topology.md @@ -6,8 +6,6 @@ linkTitle: "服务拓扑图" weight: 6915 --- -## 什么是服务拓扑图 - 您可以启用服务拓扑图以集成 [Weave Scope](https://www.weave.works/oss/scope/)（Docker 和 Kubernetes 的可视化和监控工具）。Weave Scope 使用既定的 API 收集信息，为应用和容器构建拓扑图。服务拓扑图显示在您的项目中，将服务之间的连接关系可视化。 ## 安装前启用服务拓扑图 @@ -78,7 +76,7 @@ weight: 6915 自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 {{}} -3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑配置文件**。 +3. 在**资源列表**中，点击 `ks-installer` 右侧的 ，然后选择**编辑配置文件**。 4. 在该配置文件中，搜寻到 `network`，将 `network.topology.type` 更改为 `weave-scope`。完成后，点击右下角的**更新**保存配置。 @@ -94,8 +92,9 @@ weight: 6915 kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f ``` - {{< notice tip >}} -您可以通过点击控制台右下角的锤子图标来找到 Web kubectl 工具。 + {{< notice note >}} + +您可以通过点击控制台右下角的 来找到 Web kubectl 工具。 {{}} ## 验证组件的安装 @@ -106,7 +105,7 @@ weight: 6915 进入一个项目中，导航到**应用负载**下的**服务**，即可看到**拓扑图**选项卡下**服务**的拓扑图。 -![topology1](/images/docs/zh-cn/enable-pluggable-components/service-topology/topology1.png) +![topology1](/images/docs/zh-cn/enable-pluggable-components/service-topology/topology.png) {{}} diff --git a/static/images/docs/enable-pluggable-components/kubeedge/hammer.png b/static/images/docs/enable-pluggable-components/kubeedge/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubeedge/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubeedge/three-dots.png b/static/images/docs/enable-pluggable-components/kubeedge/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubeedge/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-alerting/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-alerting/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-alerting/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-app-store/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-app-store/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-app-store/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-app-store/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-app-store/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-app-store/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-app-store/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-app-store/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-app-store/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-app-store/openpitrix.png b/static/images/docs/enable-pluggable-components/kubesphere-app-store/openpitrix.png deleted file mode 100644 index 15d470b76..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-app-store/openpitrix.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-events/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-events/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-events/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-events/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-events/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-events/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-events/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-events/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-events/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.png b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/hammer.png b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/metrics-server/clusters-management.png b/static/images/docs/enable-pluggable-components/metrics-server/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/metrics-server/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/metrics-server/edit-yaml.png b/static/images/docs/enable-pluggable-components/metrics-server/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/metrics-server/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/metrics-server/hammer.png b/static/images/docs/enable-pluggable-components/metrics-server/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/metrics-server/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/metrics-server/three-dots.png b/static/images/docs/enable-pluggable-components/metrics-server/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/metrics-server/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/network-policies/clusters-management.png b/static/images/docs/enable-pluggable-components/network-policies/clusters-management.png deleted file mode 100644 index 0ddaa4e86..000000000 Binary files a/static/images/docs/enable-pluggable-components/network-policies/clusters-management.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/network-policies/edit-yaml.png b/static/images/docs/enable-pluggable-components/network-policies/edit-yaml.png deleted file mode 100644 index 324c755ec..000000000 Binary files a/static/images/docs/enable-pluggable-components/network-policies/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/enable-pluggable-components/network-policies/hammer.png b/static/images/docs/enable-pluggable-components/network-policies/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/network-policies/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/network-policies/three-dots.png b/static/images/docs/enable-pluggable-components/network-policies/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/network-policies/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/pod-ip-pools/hammer.png b/static/images/docs/enable-pluggable-components/pod-ip-pools/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/pod-ip-pools/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png b/static/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png differ diff --git a/static/images/docs/enable-pluggable-components/service-topology/hammer.png b/static/images/docs/enable-pluggable-components/service-topology/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/enable-pluggable-components/service-topology/hammer.png differ diff --git a/static/images/docs/enable-pluggable-components/service-topology/three-dots.png b/static/images/docs/enable-pluggable-components/service-topology/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/enable-pluggable-components/service-topology/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting.PNG deleted file mode 100644 index 1f2becf70..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/cluster-management1.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/cluster-management1.png deleted file mode 100644 index 18c71c15b..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/cluster-management1.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml1.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml1.png deleted file mode 100644 index 05847dd15..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/edit-yaml1.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting1.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/alerting-section.png similarity index 100% rename from static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting-and-notification/alerting1.png rename to static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/alerting-section.png diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/openpitrix.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/openpitrix.PNG deleted file mode 100644 index 4bb0a604d..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/openpitrix.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/clusters-management.png deleted file mode 100644 index 3f41bd4d6..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/edit-yaml.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/edit-yaml.png deleted file mode 100644 index fbd14bda3..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-metrics-server/edit-yaml.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/metrics-server/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/clusters-management.png b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/clusters-management.png deleted file mode 100644 index 5dc7d15de..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/clusters-management.png and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/edit-yaml.PNG b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/edit-yaml.PNG deleted file mode 100644 index 0475c20ea..000000000 Binary files a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/edit-yaml.PNG and /dev/null differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/network-policies/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/network-policies/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/service-topology/hammer.png b/static/images/docs/zh-cn/enable-pluggable-components/service-topology/hammer.png new file mode 100644 index 000000000..d484a80de Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/service-topology/hammer.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png b/static/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png new file mode 100644 index 000000000..4ef8b9b46 Binary files /dev/null and b/static/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png differ diff --git a/static/images/docs/zh-cn/enable-pluggable-components/service-topology/topology1.png b/static/images/docs/zh-cn/enable-pluggable-components/service-topology/topology.png similarity index 100% rename from static/images/docs/zh-cn/enable-pluggable-components/service-topology/topology1.png rename to static/images/docs/zh-cn/enable-pluggable-components/service-topology/topology.png