15308555518/ website
1
0
Fork 0
mirror of https://github.com/kubesphere/website.git synced 2025-12-25 15:32:54 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update enable pluggable components docs. 

Signed-off-by: serenashe <serenashe@yunify.com>
This commit is contained in:
serenashe 2021-10-09 18:09:47 +08:00 committed by Felixnoo
parent 03bf3f75ec
commit 53fa90dfe9
83 changed files with 170 additions and 218 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/devops-user-guide/how-to-use/set-ci-node.md
View File

@ -20,7 +20,7 @@ You need an account granted a role including the permission of **Cluster Managem
2. If you have enabled the [multi-cluster feature](../../../multicluster-management/) with Member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly. 2. If you have enabled the [multi-cluster feature](../../../multicluster-management/) with Member clusters imported, you can select a specific cluster to view its nodes. If you have not enabled the feature, refer to the next step directly.
3. Navigate to **Cluster Nodes** under **Node Management**, where you can see existing nodes in the current cluster. 3. Navigate to **Cluster Nodes** under **Nodes**, where you can see existing nodes in the current cluster.
![Node Management](/images/docs/devops-user-guide/using-devops/set-ci-node-for-dependency-cache/set-node-1.png) ![Node Management](/images/docs/devops-user-guide/using-devops/set-ci-node-for-dependency-cache/set-node-1.png)

2
content/en/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md
View File

@ -111,6 +111,6 @@ Before you use Istio-based features of KubeSphere, you have to delete `applicati
{{</ notice >}} {{</ notice >}}
After your component is installed, go to the **Cluster Management** page, and you will see the interface below. You can check the status of your component in **Components**. After your component is installed, go to the **Cluster Management** page, and you will see the interface below. You can check the status of your component in **System Components**.
![Full View of KubeSphere Console](/images/docs/huawei-cce/en/view-ks-console-full.png) ![Full View of KubeSphere Console](/images/docs/huawei-cce/en/view-ks-console-full.png)

2
content/en/docs/installing-on-linux/cluster-operation/add-edge-nodes.md
View File

@ -92,7 +92,7 @@ To make sure edge nodes can successfully talk to your cluster, you must forward
1. Log in to the console as `admin` and click **Platform** in the top-left corner. 1. Log in to the console as `admin` and click **Platform** in the top-left corner.
2. Select **Cluster Management** and navigate to **Edge Nodes** under **Node Management**. 2. Select **Cluster Management** and navigate to **Edge Nodes** under **Nodes**.
{{< notice note >}} {{< notice note >}}

2
content/en/docs/installing-on-linux/cluster-operation/remove-nodes.md
View File

@ -10,7 +10,7 @@ weight: 3620
Marking a node as unschedulable prevents the scheduler from placing new Pods onto that node while not affecting existing Pods on the node. This is useful as a preparatory step before a node reboot or other maintenance. Marking a node as unschedulable prevents the scheduler from placing new Pods onto that node while not affecting existing Pods on the node. This is useful as a preparatory step before a node reboot or other maintenance.
Log in to the console as `admin` and go to the **Cluster Management** page. To mark a node unschedulable, choose **Cluster Nodes** under **Node Management** from the left menu, find a node you want to remove from the cluster, and click **Cordon**. Alternatively, you can run the command `kubectl cordon $NODENAME` directly. See [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) for more details. Log in to the console as `admin` and go to the **Cluster Management** page. To mark a node unschedulable, choose **Cluster Nodes** under **Nodes** from the left menu, find a node you want to remove from the cluster, and click **Cordon**. Alternatively, you can run the command `kubectl cordon $NODENAME` directly. See [Kubernetes Nodes](https://kubernetes.io/docs/concepts/architecture/nodes/) for more details.
![cordon](/images/docs/installing-on-linux/add-and-delete-nodes/delete-nodes/cordon.png) ![cordon](/images/docs/installing-on-linux/add-and-delete-nodes/delete-nodes/cordon.png)

12
content/en/docs/pluggable-components/alerting.md
View File

@ -8,7 +8,7 @@ weight: 6600
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. 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 ## Enable Alerting Before Installation
### Installing on Linux ### Installing on Linux
@ -62,9 +62,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable Alerting after Installation ## Enable Alerting After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -74,7 +74,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `alerting` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
alerting: alerting:
@ -89,14 +89,12 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-alerting/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
If you can see **Alerting Messages** and **Alerting Policies** on the **Cluster Management** page, it means the installation is successful as the two parts won't display until the component is installed. If you can see **Alerting Messages** and **Alerting Policies** on the **Cluster Management** page, it means the installation is successful as the two parts won't display until the component is installed.
![alerting-section](/images/docs/enable-pluggable-components/kubesphere-alerting/alerting-section.png)

20
content/en/docs/pluggable-components/app-store.md
View File

@ -10,11 +10,9 @@ As an open-source and app-centric container platform, KubeSphere provides users
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 17 built-in apps in the App Store. After you enable this feature, you can add more apps with app templates. 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 17 built-in apps in the App Store. After you enable this feature, you can add more apps with app templates.
![app-store](/images/docs/enable-pluggable-components/kubesphere-app-store/app-store.png)
For more information, see [App Store](../../application-store/). For more information, see [App Store](../../application-store/).
## Enable the App Store before Installation ## Enable the App Store Before Installation
### Installing on Linux ### Installing on Linux
@ -70,9 +68,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable the App Store after Installation ## Enable the App Store After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -84,7 +82,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `openpitrix` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
openpitrix: openpitrix:
@ -100,25 +98,23 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-app-store/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
After you log in to the console, if you can see **App Store** in the top-left corner and 17 built-in apps in it, it means the installation is successful. After you log in to the console, if you can see **App Store** in the upper-left corner and 17 built-in apps in it, it means the installation is successful.
![app-store](/images/docs/enable-pluggable-components/kubesphere-app-store/app-store.png)
{{< notice note >}} {{< notice note >}}
- You can even access the App Store without logging in to the console by visiting `<NodeIP>:30880/apps`. - You can even access the App Store without logging in to the console by visiting `<NodeIP>:30880/apps`.
- Different from previous versions, the **OpenPitrix** tab in KubeSphere 3.1 does not appear on the **Components** page after the App Store is enabled. - The **OpenPitrix** tab in KubeSphere 3.2 does not appear on the **System Components** page after the App Store is enabled.
{{</ notice >}} {{</ notice >}}
## Use the App Store in a Multi-cluster Architecture ## Use the App Store in a Multi-cluster Architecture
[In a multi-cluster architecture](../../multicluster-management/introduction/kubefed-in-kubesphere/), you have one Host Cluster (H Cluster) managing all Member Clusters (M Clusters). Different from other components in KubeSphere, the App Store serves as a global application pool for all clusters, including H Cluster and M Clusters. You only need to enable the App Store on the H Cluster and you can use functions related to the App Store on M Clusters directly (no matter whether the App Store is enabled on M Clusters or not), such as [app templates](../../project-user-guide/application/app-template/) and [app repositories](../../workspace-administration/app-repository/import-helm-repository/). [In a multi-cluster architecture](../../multicluster-management/introduction/kubefed-in-kubesphere/), you have one Host Cluster (H Cluster) managing all Member Clusters (M Clusters). Different from other components in KubeSphere, the App Store serves as a global application pool for all clusters, including H Cluster and M Clusters. You only need to enable the App Store on the H Cluster and you can use functions related to the App Store on M Clusters directly (no matter whether the App Store is enabled on M Clusters or not), such as [App Templates](../../project-user-guide/application/app-template/) and [App Repositories](../../workspace-administration/app-repository/import-helm-repository/).
However, if you only enable the App Store on M Clusters without enabling it on the H Cluster, you will not be able to use the App Store on any cluster in the multi-cluster architecture. However, if you only enable the App Store on M Clusters without enabling it on the H Cluster, you will not be able to use the App Store on any cluster in the multi-cluster architecture.

14
content/en/docs/pluggable-components/auditing-logs.md
View File

@ -10,7 +10,7 @@ The KubeSphere Auditing Log System provides a security-relevant chronological se
For more information, see [Auditing Log Query](../../toolbox/auditing/auditing-query/). For more information, see [Auditing Log Query](../../toolbox/auditing/auditing-query/).
## Enable Auditing Logs before Installation ## Enable Auditing Logs Before Installation
### Installing on Linux ### Installing on Linux
@ -96,9 +96,9 @@ By default, ks-installer will install Elasticsearch internally if Auditing is en
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable Auditing Logs after Installation ## Enable Auditing Logs After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -108,7 +108,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `auditing` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
auditing: auditing:
@ -139,7 +139,7 @@ By default, Elasticsearch will be installed internally if Auditing is enabled. F
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-auditing-logs/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
@ -148,9 +148,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Verify that you can use the **Auditing Operating** function from the **Toolbox** in the bottom-right corner. Verify that you can use the **Auditing Operating** function from the **Toolbox** in the lower-right corner.
![auditing-operating](/images/docs/enable-pluggable-components/kubesphere-auditing-logs/auditing-operating.png)
{{</ tab >}} {{</ tab >}}

14
content/en/docs/pluggable-components/devops.md
View File

@ -12,7 +12,7 @@ The DevOps System offers an enabling environment for users as apps can be automa
For more information, see [DevOps User Guide](../../devops-user-guide/). For more information, see [DevOps User Guide](../../devops-user-guide/).
## Enable DevOps before Installation ## Enable DevOps Before Installation
### Installing on Linux ### Installing on Linux
@ -66,9 +66,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable DevOps after Installation ## Enable DevOps After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -80,7 +80,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**.
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. 4. In this YAML file, navigate to `devops` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
devops: devops:
@ -95,7 +95,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-devops-system/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
@ -105,9 +105,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Go to **Components** and check the status of **DevOps**. You may see an image as follows: Go to **System Components** and check that all components on the **DevOps** tab page is in **Healthy** state.
![devops](/images/docs/enable-pluggable-components/kubesphere-devops-system/devops.png)
{{</ tab >}} {{</ tab >}}

16
content/en/docs/pluggable-components/events.md
View File

@ -6,11 +6,11 @@ linkTitle: "KubeSphere Events"
weight: 6500 weight: 6500
--- ---
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. 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/). For more information, see [Event Query](../../toolbox/events-query/).
## Enable Events before Installation ## Enable Events Before Installation
### Installing on Linux ### Installing on Linux
@ -98,9 +98,9 @@ By default, ks-installer will install Elasticsearch internally if Events is enab
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable Events after Installation ## Enable Events After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -112,7 +112,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `events` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
events: events:
@ -144,7 +144,7 @@ By default, Elasticsearch will be installed internally if Events is enabled. For
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-events/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-events/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
@ -154,9 +154,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Verify that you can use the **Event Search** function from the **Toolbox** in the bottom-right corner. Verify that you can use the **Event Search** function from the **Toolbox** in the lower-right corner.
![event-search](/images/docs/enable-pluggable-components/kubesphere-events/event-search.png)
{{</ tab >}} {{</ tab >}}

16
content/en/docs/pluggable-components/kubeedge.md
View File

@ -14,7 +14,7 @@ After you enable KubeEdge, you can [add edge nodes to your cluster](../../instal
![kubeedge_arch](/images/docs/enable-pluggable-components/kubeedge/kubeedge_arch.png) ![kubeedge_arch](/images/docs/enable-pluggable-components/kubeedge/kubeedge_arch.png)
## Enable KubeEdge before Installation ## Enable KubeEdge Before Installation
### Installing on Linux ### Installing on Linux
@ -72,9 +72,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable KubeEdge after Installation ## Enable KubeEdge After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -91,7 +91,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
enabled: true # Change "false" to "true". enabled: true # Change "false" to "true".
``` ```
5. Set the value of `kubeedge.cloudCore.cloudHub.advertiseAddress` to the public IP address of your cluster or an IP address that can be accessed by edge nodes. After you finish, click **Update** in the bottom-right corner to save the configuration. 5. Set the value of `kubeedge.cloudCore.cloudHub.advertiseAddress` to the public IP address of your cluster or an IP address that can be accessed by edge nodes. After you finish, click **OK** in the lower-right corner to save the configuration.
{{< notice note >}} {{< notice note >}}
@ -107,10 +107,10 @@ The `kubeedge` section is not included in `cluster-configuration.yaml` if your c
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubeedge/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubeedge/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Enable KubeEdge after Upgrade ## Enable KubeEdge After Upgrade
If your KubeSphere v3.1.0 cluster is upgraded from KubeSphere v3.0.0, add the following content in `cluster-configuration.yaml` (i.e. the `clusterconfiguration` CRD) and enable `kubeedge` as shown [in the steps above](#enable-kubeedge-after-installation). If your KubeSphere v3.1.0 cluster is upgraded from KubeSphere v3.0.0, add the following content in `cluster-configuration.yaml` (i.e. the `clusterconfiguration` CRD) and enable `kubeedge` as shown [in the steps above](#enable-kubeedge-after-installation).
@ -155,9 +155,7 @@ Do not add the `kubeedge` section in `cluster-configuration.yaml` before the upg
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
On the **Cluster Management** page, verify that the section **Edge Nodes** has appeared under **Node Management**. On the **Cluster Management** page, verify that the **Edge Nodes** module has appeared under **Nodes**.
![edge-nodes](/images/docs/enable-pluggable-components/kubeedge/edge-nodes.png)
{{</ tab >}} {{</ tab >}}

14
content/en/docs/pluggable-components/logging.md
View File

@ -10,7 +10,7 @@ KubeSphere provides a powerful, holistic and easy-to-use logging system for log
For more information, see [Log Query](../../toolbox/log-query/). For more information, see [Log Query](../../toolbox/log-query/).
## Enable Logging before Installation ## Enable Logging Before Installation
### Installing on Linux ### Installing on Linux
@ -100,9 +100,9 @@ By default, ks-installer will install Elasticsearch internally if Logging is ena
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable Logging after Installation ## Enable Logging After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -114,7 +114,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `logging` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
logging: logging:
@ -145,7 +145,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-logging-system/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
@ -155,9 +155,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Go to **Components** and check the status of **Logging**. You may see an image as follows: Go to **System Components** and check that all components on the **Logging** tab page is in **Healthy** state.
![logging](/images/docs/enable-pluggable-components/kubesphere-logging-system/logging.png)
{{</ tab >}} {{</ tab >}}

10
content/en/docs/pluggable-components/metrics-server.md
View File

@ -8,7 +8,7 @@ weight: 6910
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. 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 ## Enable the Metrics Server Before Installation
### Installing on Linux ### Installing on Linux
@ -67,9 +67,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
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. 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.
{{</ notice >}} {{</ notice >}}
## Enable the Metrics Server after Installation ## Enable the Metrics Server After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -79,7 +79,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/metrics-server/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/metrics-server/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `metrics_server` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
metrics_server: metrics_server:
@ -94,7 +94,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/metrics-server/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/metrics-server/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component

16
content/en/docs/pluggable-components/network-policy.md
View File

@ -10,14 +10,14 @@ Starting from v3.0.0, users can configure network policies of native Kubernetes
{{< notice note >}} {{< notice note >}}
- Please make sure that the CNI network plugin used by the cluster supports Network Policies before you enable the feature. There are a number of CNI network plugins that support Network Policies, including Calico, Cilium, Kube-router, Romana and Weave Net. - Please make sure that the CNI network plugin used by the cluster supports Network Policies before you enable the feature. There are a number of CNI network plugins that support Network Policies, including Calico, Cilium, Kube-router, Romana, and Weave Net.
- It is recommended that you use [Calico](https://www.projectcalico.org/) as the CNI plugin before you enable Network Policies. - It is recommended that you use [Calico](https://www.projectcalico.org/) as the CNI plugin before you enable Network Policies.
{{</ notice >}} {{</ notice >}}
For more information, see [Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/). For more information, see [Network Policies](https://kubernetes.io/docs/concepts/services-networking/network-policies/).
## Enable the Network Policy before Installation ## Enable the Network Policy Before Installation
### Installing on Linux ### Installing on Linux
@ -73,9 +73,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable the Network Policy after Installation ## Enable the Network Policy After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -85,7 +85,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `network.networkpolicy` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
network: network:
@ -101,11 +101,9 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/network-policies/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/network-policies/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
If you can see **Network Policies** in **Network** as the image below, it means the installation succeeds as this part won't display until you install the component. If you can see the **Network Policies** module in **Network**, it means the installation is successful as this part won't display until you install the component.
![networkpolicy](/images/docs/enable-pluggable-components/network-policies/networkpolicy.png)

14
content/en/docs/pluggable-components/pod-ip-pools.md
View File

@ -8,7 +8,7 @@ weight: 6920
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. 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 ## Enable Pod IP Pools Before Installation
### Installing on Linux ### Installing on Linux
@ -65,9 +65,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
``` ```
## Enable Pod IP Pools after Installation ## Enable Pod IP Pools After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -77,7 +77,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `network` and change `network.ippool.type` to `calico`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
network: network:
@ -93,14 +93,12 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/pod-ip-pools/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/pod-ip-pools/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
On the **Cluster Management** page, verify that you can see the section **Pod IP Pools** under **Network**. On the **Cluster Management** page, verify that you can see the **Pod IP Pools** module under **Network**.
![pod-ip-pool](/images/docs/enable-pluggable-components/pod-ip-pools/pod-ip-pool.png)

16
content/en/docs/pluggable-components/service-mesh.md
View File

@ -6,11 +6,11 @@ linkTitle: "KubeSphere Service Mesh"
weight: 6800 weight: 6800
--- ---
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. 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/). For more information, see [Grayscale Release](../../project-user-guide/grayscale-release/overview/).
## Enable KubeSphere Service Mesh before Installation ## Enable KubeSphere Service Mesh Before Installation
### Installing on Linux ### Installing on Linux
@ -64,9 +64,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
## Enable KubeSphere Service Mesh after Installation ## Enable KubeSphere Service Mesh After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -76,7 +76,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `servicemesh` and change `false` to `true` for `enabled`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
servicemesh: servicemesh:
@ -91,7 +91,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/kubesphere-service-mesh/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
@ -100,9 +100,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Go to **Components** and check the status of **Istio**. You may see an image as follows: Go to **System Components** and check that all components on the **Istio** tab page is in **Healthy** state.
![istio](/images/docs/enable-pluggable-components/kubesphere-service-mesh/istio.png)
{{</ tab >}} {{</ tab >}}

14
content/en/docs/pluggable-components/service-topology.md
View File

@ -8,7 +8,7 @@ weight: 6915
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. 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 ## Enable Service Topology Before Installation
### Installing on Linux ### Installing on Linux
@ -65,9 +65,9 @@ As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introdu
``` ```
## Enable Service Topology after Installation ## Enable Service Topology After Installation
1. Log in to the console as `admin`. Click **Platform** in the top-left corner and select **Cluster Management**. 1. Log in to the console as `admin`. Click **Platform** in the upper-left corner and select **Cluster Management**.
2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page. 2. Click **CRDs** and enter `clusterconfiguration` in the search bar. Click the result to view its detail page.
@ -77,7 +77,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/service-topology/three-dots.png" height="20px"> on the right of `ks-installer` and select **Edit YAML**. 3. In **Resource List**, click <img src="/images/docs/enable-pluggable-components/service-topology/three-dots.png" height="20px"> 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. 4. In this YAML file, navigate to `network` and change `network.topology.type` to `weave-scope`. After you finish, click **OK** in the lower-right corner to save the configuration.
```yaml ```yaml
network: network:
@ -93,7 +93,7 @@ A Custom Resource Definition (CRD) allows users to create a new type of resource
{{< notice note >}} {{< notice note >}}
You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/service-topology/hammer.png" height="20px"> in the bottom-right corner of the console. You can find the web kubectl tool by clicking <img src="/images/docs/enable-pluggable-components/service-topology/hammer.png" height="20px"> in the lower-right corner of the console.
{{</ notice >}} {{</ notice >}}
## Verify the Installation of the Component ## Verify the Installation of the Component
@ -102,9 +102,7 @@ You can find the web kubectl tool by clicking <img src="/images/docs/enable-plug
{{< tab "Verify the component on the dashboard" >}} {{< tab "Verify the component on the dashboard" >}}
Go to one of your project, navigate to **Services** under **Application Workloads**, and you can see a topology of your **Services** on the **Topology** tab. Go to one of your project, navigate to **Services** under **Application Workloads**, and you can see a topology of your Services on the **Service Topology** tab page.
![topology](/images/docs/enable-pluggable-components/service-topology/topology.png)
{{</ tab >}} {{</ tab >}}

10
content/en/docs/pluggable-components/uninstall-pluggable-components.md
View File

@ -1,8 +1,8 @@
--- ---
title: "Uninstall Pluggable Components from KubeSphere v3.1.x" title: "Uninstall Pluggable Components from KubeSphere v3.2.0"
keywords: "Installer, uninstall, KubeSphere, Kubernetes" keywords: "Installer, uninstall, KubeSphere, Kubernetes"
description: "Learn how to uninstall each pluggable component in KubeSphere v3.1.x." description: "Learn how to uninstall each pluggable component in KubeSphere v3.2.0."
linkTitle: "Uninstall Pluggable Components from KubeSphere v3.1.x" linkTitle: "Uninstall Pluggable Components from KubeSphere v3.2.0"
Weight: 6940 Weight: 6940
--- ---
@ -10,7 +10,7 @@ After you [enable the pluggable components of KubeSphere](../../pluggable-compon
{{< notice note >}} {{< notice note >}}
The methods of uninstalling certain pluggable components on KubeSphere v3.1.x are different from the methods on KubeSphere v3.0.0. For more information about the uninstallation methods on KubeSphere v3.0.0, see [Uninstall Pluggable Components from KubeSphere](https://v3-0.docs.kubesphere.io/docs/faq/installation/uninstall-pluggable-components/). The methods of uninstalling certain pluggable components on KubeSphere v3.2.0 are different from the methods on KubeSphere v3.0.0. For more information about the uninstallation methods on KubeSphere v3.0.0, see [Uninstall Pluggable Components from KubeSphere](https://v3-0.docs.kubesphere.io/docs/faq/installation/uninstall-pluggable-components/).
{{</ notice >}} {{</ notice >}}
@ -146,7 +146,7 @@ Change the value of `openpitrix.store.enabled` from `true` to `false` in `ks-ins
{{< notice note >}} {{< notice note >}}
Notification is installed in KubeSphere v3.1.x by default, so you do not need to uninstall it. Notification is installed in KubeSphere v3.2.0 by default, so you do not need to uninstall it.
{{</ notice >}} {{</ notice >}}

2
content/en/docs/project-user-guide/application/compose-app.md
View File

@ -21,7 +21,7 @@ This tutorial demonstrates how to create a microservices-based app Bookinfo, whi
2. Set a name for the app (for example, `bookinfo`) and click **Next**. 2. Set a name for the app (for example, `bookinfo`) and click **Next**.
3. On the **Components** page, you need to create microservices that compose the app. Click **Add Service** and select **Stateless Service**. 3. On the **System Components** page, you need to create microservices that compose the app. Click **Add Service** and select **Stateless Service**.
4. Set a name for the Service (e.g `productpage`) and click **Next**. 4. Set a name for the Service (e.g `productpage`) and click **Next**.

2
content/en/docs/quick-start/all-in-one-on-linux.md
View File

@ -259,7 +259,7 @@ You may need to configure port forwarding rules and open the port in your securi
{{</ notice >}} {{</ notice >}}
After logging in to the console, you can check the status of different components in **Components**. You may need to wait for some components to be up and running if you want to use related services. You can also use `kubectl get pod --all-namespaces` to inspect the running status of KubeSphere workloads. After logging in to the console, you can check the status of different components in **System Components**. You may need to wait for some components to be up and running if you want to use related services. You can also use `kubectl get pod --all-namespaces` to inspect the running status of KubeSphere workloads.
![kubesphere-components](/images/docs/quickstart/all-in-one-installation/kubesphere-components.png) ![kubesphere-components](/images/docs/quickstart/all-in-one-installation/kubesphere-components.png)

4
content/en/docs/quick-start/enable-pluggable-components.md
View File

@ -78,7 +78,7 @@ When you install KubeSphere on Kubernetes, you need to use [ks-installer](https:
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
Whether you install KubeSphere on Linux or on Kubernetes, you can check the status of the components you have enabled in the web console of KubeSphere after installation. Go to **Components**, and you can see an image below: Whether you install KubeSphere on Linux or on Kubernetes, you can check the status of the components you have enabled in the web console of KubeSphere after installation. Go to **System Components**, and you can see an image below:
![component-status](/images/docs/quickstart/enable-pluggable-components/component-status.png) ![component-status](/images/docs/quickstart/enable-pluggable-components/component-status.png)
@ -140,7 +140,7 @@ You can find the web kubectl tool by clicking the hammer icon in the bottom-righ
##################################################### #####################################################
``` ```
7. In **Components**, you can see the status of different components. 7. In **System Components**, you can see the status of different components.
![component-status-page](/images/docs/quickstart/enable-pluggable-components/component-status-page.png) ![component-status-page](/images/docs/quickstart/enable-pluggable-components/component-status-page.png)

2
content/en/docs/quick-start/minimal-kubesphere-on-k8s.md
View File

@ -52,7 +52,7 @@ After you make sure your machine meets the conditions, perform the following ste
4. Make sure port `30880` is opened in your security group and access the web console through the NodePort (`IP:30880`) with the default account and password (`admin/P@88w0rd`). 4. Make sure port `30880` is opened in your security group and access the web console through the NodePort (`IP:30880`) with the default account and password (`admin/P@88w0rd`).
5. After logging in to the console, you can check the status of different components in **Components**. You may need to wait for some components to be up and running if you want to use related services. 5. After logging in to the console, you can check the status of different components in **System Components**. You may need to wait for some components to be up and running if you want to use related services.
![kubesphere-components](/images/docs/quickstart/minimal-installation-on-k8s/kubesphere-components.png) ![kubesphere-components](/images/docs/quickstart/minimal-installation-on-k8s/kubesphere-components.png)

2
content/en/docs/quick-start/wordpress-deployment.md
View File

@ -72,7 +72,7 @@ Follow the same steps above to create a WordPress Secret `wordpress-secret` with
![basic-info1](/images/docs/quickstart/wordpress-deployment/basic-info1.png) ![basic-info1](/images/docs/quickstart/wordpress-deployment/basic-info1.png)
3. In **Components**, click **Add Service** to set a component in the app. 3. In **System Components**, click **Add Service** to set a component in the app.
![add-service1](/images/docs/quickstart/wordpress-deployment/add-service1.png) ![add-service1](/images/docs/quickstart/wordpress-deployment/add-service1.png)

4
content/zh/blogs/changhong-kubernetes-autoscaling-canaryrelease.md
View File

@ -107,13 +107,13 @@ CA 依赖于云平台的能力，而通过设置 HPA 可以触发 CA。在 KubeS
由于我们是先部署好 Kubernetes，在其上再安装 KubeSphere的，那么我们需要在安装后的 KubeSphere 启用该功能。 由于我们是先部署好 Kubernetes，在其上再安装 KubeSphere的，那么我们需要在安装后的 KubeSphere 启用该功能。
启用方法： 启用方法：
1. 在 KubeSphere 的集群管理界面，找到自定义资源 CRD 1. 在 KubeSphere 的集群管理界面，找到 CRD
2. 打开后输入 `clusterconfiguration` 进行搜索 2. 打开后输入 `clusterconfiguration` 进行搜索
3. 点击搜索结果，在打开的页面中点击 ks-installer 右侧的按钮，选择编辑配置文件 3. 点击搜索结果，在打开的页面中点击 ks-installer 右侧的按钮，选择编辑配置文件
4. 在打开的 YAML 文件里找到 Metrics Server，在 enabled 一行将 false 更改为 true 4. 在打开的 YAML 文件里找到 Metrics Server，在 enabled 一行将 false 更改为 true
5. 之后点击右下角的更新即可 5. 之后点击右下角的更新即可
![自定义资源 CRD](https://pek3b.qingstor.com/kubesphere-community/images/CRD-changhong.png) ![ CRD](https://pek3b.qingstor.com/kubesphere-community/images/CRD-changhong.png)
![修改 YAML 文件](https://pek3b.qingstor.com/kubesphere-community/images/yaml-changhong.png) ![修改 YAML 文件](https://pek3b.qingstor.com/kubesphere-community/images/yaml-changhong.png)

2
content/zh/blogs/kubesphere-core-architecture.md
View File

@ -144,7 +144,7 @@ subjects:
### CRD + controller ### CRD + controller
自定义资源（Custom Resource） 是对 Kubernetes API 的扩展，可以通过动态注册的方式拓展 K8s API。用户可以使用 kubectl 来创建和访问其中的对象，就像操作内置资源一样。 定制资源（Custom Resource） 是对 Kubernetes API 的扩展，可以通过动态注册的方式拓展 K8s API。用户可以使用 kubectl 来创建和访问其中的对象，就像操作内置资源一样。
通过 CRD 对资源进行抽象，再通过 controller 监听资源变化维护资源状态， controller 的核心是 Reconcile，与他的意思一样，通过被动、定时触发的方式对资源状态进行维护，直至达到声明的状态。 通过 CRD 对资源进行抽象，再通过 controller 监听资源变化维护资源状态， controller 的核心是 Reconcile，与他的意思一样，通过被动、定时触发的方式对资源状态进行维护，直至达到声明的状态。

2
content/zh/docs/application-store/app-developer-guide/helm-specification.md
View File

@ -20,7 +20,7 @@ chartname/
values.yaml # 该 Chart 的默认配置值。 values.yaml # 该 Chart 的默认配置值。
values.schema.json # （可选）向 values.yaml 文件添加结构的 JSON Schema。 values.schema.json # （可选）向 values.yaml 文件添加结构的 JSON Schema。
charts/ # 一个目录，包含该 Chart 所依赖的任意 Chart。 charts/ # 一个目录，包含该 Chart 所依赖的任意 Chart。
crds/ # 自定义资源定义。 crds/ # 定制资源定义。
templates/ # 模板的目录，若提供相应值便可以生成有效的 Kubernetes 配置文件。 templates/ # 模板的目录，若提供相应值便可以生成有效的 Kubernetes 配置文件。
templates/NOTES.txt # （可选）包含使用说明的纯文本文件。 templates/NOTES.txt # （可选）包含使用说明的纯文本文件。
``` ```

2
content/zh/docs/cluster-administration/cluster-status-monitoring.md
View File

@ -49,7 +49,7 @@ KubeSphere 监控集群中各种服务组件的健康状态。当关键组件发
1. 在**集群状态监控**页面，点击**组件状态**区域的组件以查看其状态。 1. 在**集群状态监控**页面，点击**组件状态**区域的组件以查看其状态。
![component-monitoring](/images/docs/zh-cn/cluster-administration/cluster-status-monitoring/component-monitoring.png) ![component-monitoring](/images/docs/zh-cn/cluster-administration/cluster-status-monitoring/component-monitoring.png)
2. **服务组件**页面列出了所有的组件。标记为绿色的组件是正常运行的组件，标记为橙色的组件存在问题，需要特别关注。 2. **系统组件**页面列出了所有的组件。标记为绿色的组件是正常运行的组件，标记为橙色的组件存在问题，需要特别关注。
![Service Components Status](/images/docs/zh-cn/cluster-administration/cluster-status-monitoring/service-components-status.png) ![Service Components Status](/images/docs/zh-cn/cluster-administration/cluster-status-monitoring/service-components-status.png)
{{< notice tip >}} {{< notice tip >}}

2
content/zh/docs/cluster-administration/nodes.md
View File

@ -25,7 +25,7 @@ Kubernetes 将容器放入 Pod 中并在节点上运行，从而运行工作负
2. 如果您已启用了[多集群功能](../../multicluster-management/)并已导入了 Member 集群，您可以选择一个特定集群以查看其节点信息。如果尚未启用该功能，请直接进行下一步。 2. 如果您已启用了[多集群功能](../../multicluster-management/)并已导入了 Member 集群，您可以选择一个特定集群以查看其节点信息。如果尚未启用该功能，请直接进行下一步。
![cluster-management1](/images/docs/zh-cn/cluster-administration/node-management/cluster-management1.png) ![cluster-management1](/images/docs/zh-cn/cluster-administration/node-management/cluster-management1.png)
3. 在左侧导航栏中选择**节点管理**下的**集群节点**，查看节点的状态详情。 3. 在左侧导航栏中选择**节点**下的**集群节点**，查看节点的状态详情。
![Node-Status](/images/docs/zh-cn/cluster-administration/node-management/Node-Status.png) ![Node-Status](/images/docs/zh-cn/cluster-administration/node-management/Node-Status.png)

2
content/zh/docs/devops-user-guide/how-to-use/set-ci-node.md
View File

@ -20,7 +20,7 @@ weight: 11270
2. 如果您已经启用[多集群功能](../../../multicluster-management/)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。 2. 如果您已经启用[多集群功能](../../../multicluster-management/)并已导入 Member 集群，那么您可以选择一个特定集群以查看其节点。如果尚未启用该功能，请直接参考下一步。
3. 转到**节点管理**下的**集群节点**，您可以在其中查看当前集群中的现有节点。 3. 转到**节点**下的**集群节点**，您可以在其中查看当前集群中的现有节点。
![节点管理](/images/docs/zh-cn/devops-user-guide/use-devops/set-ci-node-for-dependency-caching/node-management.png) ![节点管理](/images/docs/zh-cn/devops-user-guide/use-devops/set-ci-node-for-dependency-caching/node-management.png)

2
content/zh/docs/faq/installation/telemetry.md
View File

@ -66,7 +66,7 @@ Telemetry 收集已安装 KubeSphere 集群的大小、KubeSphere 和 Kubernetes
1. 以 `admin` 用户登录控制台，点击页面左上角的**平台管理**。 1. 以 `admin` 用户登录控制台，点击页面左上角的**平台管理**。
2. 选择**集群管理**，在左侧导航栏中点击**自定义资源 CRD**。 2. 选择**集群管理**，在左侧导航栏中点击 **CRD**。
{{< notice note >}} {{< notice note >}}
如果[多集群功能](../../../multicluster-management/)已经启用，您需要先选择一个集群。 如果[多集群功能](../../../multicluster-management/)已经启用，您需要先选择一个集群。

4
content/zh/docs/installing-on-kubernetes/hosted-kubernetes/install-kubesphere-on-huaweicloud-cce.md
View File

@ -86,7 +86,7 @@ kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3
通过 `kubesphere-system` 命名空间下的 Pod 运行状态确认 KubeSphere 基础组件都已进入运行状态后，我们需要为 KubeSphere 控制台开启外网访问。 通过 `kubesphere-system` 命名空间下的 Pod 运行状态确认 KubeSphere 基础组件都已进入运行状态后，我们需要为 KubeSphere 控制台开启外网访问。
进入**资源管理** > **网络管理**，在右侧面板中选择 `ks-console` 更改网络访问方式，建议选用 `负载均衡（LoadBalancer` 访问方式（需绑定弹性公网 IP），配置完成后如下图： 进入**资源管理** > **网络**，在右侧面板中选择 `ks-console` 更改网络访问方式，建议选用 `负载均衡（LoadBalancer` 访问方式（需绑定弹性公网 IP），配置完成后如下图：
![开启 KubeSphere 外网访问](/images/docs/huawei-cce/zh/expose-ks-console.png) ![开启 KubeSphere 外网访问](/images/docs/huawei-cce/zh/expose-ks-console.png)
@ -104,7 +104,7 @@ kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3
{{< notice warning >}} {{< notice warning >}}
在开启 Istio 组件之前，由于自定义资源定义 (CRD) 冲突的问题，需要先删除华为 CCE 自带的 `applications.app.k8s.io` ，最直接的方式是通过 kubectl 工具来完成： 在开启 Istio 组件之前，由于定制资源定义（CRD）冲突的问题，需要先删除华为 CCE 自带的 `applications.app.k8s.io` ，最直接的方式是通过 kubectl 工具来完成：
```bash ```bash
kubectl delete crd applications.app.k8s.io kubectl delete crd applications.app.k8s.io

2
content/zh/docs/installing-on-linux/cluster-operation/add-edge-nodes.md
View File

@ -92,7 +92,7 @@ KubeSphere 利用 [KubeEdge](https://kubeedge.io/zh/) 将原生容器化应用
1. 使用 `admin` 用户登录控制台，点击左上角的**平台管理**。 1. 使用 `admin` 用户登录控制台，点击左上角的**平台管理**。
2. 选择**集群管理**，然后导航至**节点管理**下的**边缘节点**。 2. 选择**集群管理**，然后导航至**节点**下的**边缘节点**。
{{< notice note >}} {{< notice note >}}

2
content/zh/docs/installing-on-linux/cluster-operation/add-new-nodes.md
View File

@ -66,7 +66,7 @@ KubeSphere 使用一段时间之后，由于工作负载不断增加，您可能
./kk add nodes -f sample.yaml ./kk add nodes -f sample.yaml
``` ```
4. 安装完成后，您将能够在 KubeSphere 的控制台上查看新节点及其信息。在**集群管理**页面，选择左侧菜单**节点管理**下的**集群节点**，或者执行命令 `kubectl get node` 以检查更改。 4. 安装完成后，您将能够在 KubeSphere 的控制台上查看新节点及其信息。在**集群管理**页面，选择左侧菜单**节点**下的**集群节点**，或者执行命令 `kubectl get node` 以检查更改。
```bash ```bash
$ kubectl get node $ kubectl get node

2
content/zh/docs/installing-on-linux/cluster-operation/remove-nodes.md
View File

@ -10,7 +10,7 @@ weight: 3620
将节点标记为不可调度可防止调度程序将新的 Pod 放置到该节点上，同时不会影响该节点上的现有 Pod。作为节点重启或者其他维护之前的准备步骤，这十分有用。 将节点标记为不可调度可防止调度程序将新的 Pod 放置到该节点上，同时不会影响该节点上的现有 Pod。作为节点重启或者其他维护之前的准备步骤，这十分有用。
以 `admin` 身份登录控制台，访问**集群管理**页面。若要将节点标记为不可调度，从左侧菜单中选择**节点管理**下的**集群节点**，找到想要从集群中删除的节点，点击**停止调度**。或者，直接执行命令 `kubectl cordon $NODENAME`。有关更多详细信息，请参见 [Kubernetes 节点](https://kubernetes.io/docs/concepts/architecture/nodes/)。 以 `admin` 身份登录控制台，访问**集群管理**页面。若要将节点标记为不可调度，从左侧菜单中选择**节点**下的**集群节点**，找到想要从集群中删除的节点，点击**停止调度**。或者，直接执行命令 `kubectl cordon $NODENAME`。有关更多详细信息，请参见 [Kubernetes 节点](https://kubernetes.io/docs/concepts/architecture/nodes/)。
![cordon](/images/docs/zh-cn/installing-on-linux/add-and-delete-nodes/delete-nodes/cordon.png) ![cordon](/images/docs/zh-cn/installing-on-linux/add-and-delete-nodes/delete-nodes/cordon.png)

2
content/zh/docs/installing-on-linux/public-cloud/install-kubesphere-on-ali-ecs.md
View File

@ -262,7 +262,7 @@ https://kubesphere.io 2020-08-24 23:30:06
## 如何自定义开启可插拔组件 ## 如何自定义开启可插拔组件
- 点击 `集群管理` - `自定义资源CRD` ，在过滤条件框输入 `ClusterConfiguration` ，如图： - 点击 `集群管理` - `CRD` ，在过滤条件框输入 `ClusterConfiguration` ，如图：
![修改KsInstaller](/images/docs/ali-ecs/update_crd.png) ![修改KsInstaller](/images/docs/ali-ecs/update_crd.png)

2
content/zh/docs/installing-on-linux/public-cloud/install-kubesphere-on-huaweicloud-ecs.md
View File

@ -313,7 +313,7 @@ https://kubesphere.io 2020-08-28 01:25:54
## 如何自定义开启可插拔组件 ## 如何自定义开启可插拔组件
点击 `集群管理` - `自定义资源CRD` ，在过滤条件框输入 `ClusterConfiguration` ，如图下 点击 `集群管理` - `CRD` ，在过滤条件框输入 `ClusterConfiguration` ，如图下
![5-1-自定义组件](/images/docs/huawei-ecs/huawei-crds-config.png) ![5-1-自定义组件](/images/docs/huawei-ecs/huawei-crds-config.png)
点击 `ClusterConfiguration` 详情，对 `ks-installer` 编辑保存退出即可，组件描述介绍：[文档说明](https://github.com/kubesphere/ks-installer/blob/master/deploy/cluster-configuration.yaml)。 点击 `ClusterConfiguration` 详情，对 `ks-installer` 编辑保存退出即可，组件描述介绍：[文档说明](https://github.com/kubesphere/ks-installer/blob/master/deploy/cluster-configuration.yaml)。
![5-2-自定义组件](/images/docs/huawei-ecs/huawei-crds-edit-yaml.png) ![5-2-自定义组件](/images/docs/huawei-ecs/huawei-crds-edit-yaml.png)

6
content/zh/docs/multicluster-management/enable-multicluster/agent-connection.md
View File

@ -22,7 +22,7 @@ Host 集群为您提供中央控制平面，并且您只能指定一个 Host 集
- 选项 A - 使用 Web 控制台： - 选项 A - 使用 Web 控制台：
使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的**自定义资源 CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。 使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的 **CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。
- 选项 B - 使用 Kubectl： - 选项 B - 使用 Kubectl：
@ -113,7 +113,7 @@ tower LoadBalancer 10.233.63.191 139.198.110.23 8080:30721/TCP
- 选项 A - 使用 Web 控制台： - 选项 A - 使用 Web 控制台：
使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的**自定义资源 CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。 使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的 **CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。
- 选项 B - 使用 Kubectl： - 选项 B - 使用 Kubectl：
@ -161,7 +161,7 @@ jwtSecret: "gfIwilcc0WjNGKJ5DLeksf2JKfcLgTZU"
- 选项 A - 使用 Web 控制台： - 选项 A - 使用 Web 控制台：
使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的**自定义资源 CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。 使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的 **CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。
- 选项 B - 使用 Kubectl： - 选项 B - 使用 Kubectl：

4
content/zh/docs/multicluster-management/enable-multicluster/direct-connection.md
View File

@ -22,7 +22,7 @@ Host 集群为您提供中央控制平面，并且您只能指定一个 Host 集
- 选项 A - 使用 Web 控制台： - 选项 A - 使用 Web 控制台：
使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的**自定义资源 CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。 使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的 **CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。
- 选项 B - 使用 Kubectl： - 选项 B - 使用 Kubectl：
@ -88,7 +88,7 @@ jwtSecret: "gfIwilcc0WjNGKJ5DLeksf2JKfcLgTZU"
- 选项 A - 使用 Web 控制台： - 选项 A - 使用 Web 控制台：
使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的**自定义资源 CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。 使用 `admin` 帐户登录控制台，然后进入**集群管理**页面上的 **CRD**，输入关键字 `ClusterConfiguration`，然后转到其详情页面。编辑 `ks-installer` 的 YAML 文件，方法类似于[启用可插拔组件](../../../pluggable-components/)。
- 选项 B - 使用 Kubectl： - 选项 B - 使用 Kubectl：

2
content/zh/docs/multicluster-management/import-cloud-hosted-k8s/import-aliyun-ack.md
View File

@ -31,7 +31,7 @@ weight: 5310
2. 以 `admin` 身份登录 ACK 集群的 KubeSphere 控制台。点击左上角的**平台管理**，选择**集群管理**。 2. 以 `admin` 身份登录 ACK 集群的 KubeSphere 控制台。点击左上角的**平台管理**，选择**集群管理**。
3. 访问**自定义资源 CRD**，在搜索栏输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。 3. 访问 **CRD**，在搜索栏输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。
![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-ack/search-config.png) ![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-ack/search-config.png)

2
content/zh/docs/multicluster-management/import-cloud-hosted-k8s/import-aws-eks.md
View File

@ -35,7 +35,7 @@ weight: 5320
2. 以 `admin` 身份登录 EKS 集群的 KubeSphere Web 控制台。点击左上角的**平台管理**，选择**集群管理**。 2. 以 `admin` 身份登录 EKS 集群的 KubeSphere Web 控制台。点击左上角的**平台管理**，选择**集群管理**。
3. 访问**自定义资源 CRD**，在搜索栏输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。 3. 访问 **CRD**，在搜索栏输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。
![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-eks/search-config.png) ![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-eks/search-config.png)

2
content/zh/docs/multicluster-management/import-cloud-hosted-k8s/import-gke.md
View File

@ -35,7 +35,7 @@ weight: 5330
2. 以 `admin` 身份登录 GKE 的 KubeSphere Web 控制台。点击左上角的**平台管理**，选择**集群管理**。 2. 以 `admin` 身份登录 GKE 的 KubeSphere Web 控制台。点击左上角的**平台管理**，选择**集群管理**。
3. 访问**自定义资源 CRD**，在搜索栏中输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。 3. 访问 **CRD**，在搜索栏中输入 `ClusterConfiguration`，然后按下键盘上的**回车键**。点击 **ClusterConfiguration** 访问其详情页。
![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-gke/search-config.png) ![search-config](/images/docs/zh-cn/multicluster-management/import-cloud-hosted-k8s/import-gke/search-config.png)

10
content/zh/docs/pluggable-components/alerting.md
View File

@ -66,15 +66,15 @@ weight: 6600
1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `alerting`，将 `enabled` 的 `false` 更改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `alerting`，将 `enabled` 的 `false` 更改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
alerting: alerting:
@ -94,6 +94,4 @@ weight: 6600
## 验证组件的安装 ## 验证组件的安装
如果您在**集群管理**页面可以看到**告警消息**和**告警策略**，说明安装成功，因为安装组件之后才会显示这两部分。 如果您在**集群管理**页面可以看到**告警消息**和**告警策略**，说明安装成功，因为安装组件之后才会显示这两部分。
![alerting-section](/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/alerting-section.png)

16
content/zh/docs/pluggable-components/app-store.md
View File

@ -1,6 +1,6 @@
--- ---
title: "KubeSphere 应用商店" title: "KubeSphere 应用商店"
keywords: "Kubernetes, KubeSphere, app-store, OpenPitrix" keywords: "Kubernetes, KubeSphere, App Store, OpenPitrix"
description: "了解如何启用应用商店，一个可以在内部实现数据和应用共享、并制定应用交付流程的行业标准的组件。" description: "了解如何启用应用商店，一个可以在内部实现数据和应用共享、并制定应用交付流程的行业标准的组件。"
linkTitle: "KubeSphere 应用商店" linkTitle: "KubeSphere 应用商店"
weight: 6200 weight: 6200
@ -10,8 +10,6 @@ weight: 6200
对内，KubeSphere 应用商店可以作为不同团队共享数据、中间件和办公应用的场所。对外，有利于设立构建和交付的行业标准。默认情况下，应用商店中内置了 17 个应用。启用该功能后，您可以通过应用模板添加更多应用。 对内，KubeSphere 应用商店可以作为不同团队共享数据、中间件和办公应用的场所。对外，有利于设立构建和交付的行业标准。默认情况下，应用商店中内置了 17 个应用。启用该功能后，您可以通过应用模板添加更多应用。
![app-store](/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/app-store-page.png)
有关更多信息，请参阅[应用商店](../../application-store/)。 有关更多信息，请参阅[应用商店](../../application-store/)。
## 在安装前启用应用商店 ## 在安装前启用应用商店
@ -46,7 +44,7 @@ weight: 6200
### 在 Kubernetes 上安装 ### 在 Kubernetes 上安装
[在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用应用商店（可选服务组件）。 [在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用应用商店（可选系统组件）。
1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。 1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。
@ -74,15 +72,15 @@ weight: 6200
1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`，点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `openpitrix`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `openpitrix`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
openpitrix: openpitrix:
@ -105,12 +103,10 @@ weight: 6200
在您登录控制台后，如果您能看到页面左上角的**应用商店**以及其中的 17 个内置应用，则说明安装成功。 在您登录控制台后，如果您能看到页面左上角的**应用商店**以及其中的 17 个内置应用，则说明安装成功。
![app-store](/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/app-store-page.png)
{{< notice note >}} {{< notice note >}}
- 您可以在不登录控制台的情况下直接访问 `<NodeIP>:30880/apps` 进入应用商店。 - 您可以在不登录控制台的情况下直接访问 `<NodeIP>:30880/apps` 进入应用商店。
- 与先前版本不同，KubeSphere 3.1 中的应用商店启用后，**OpenPitrix** 选项卡不会显示在**服务组件**页面。 - KubeSphere 3.2 中的应用商店启用后，**OpenPitrix** 页签不会显示在**系统组件**页面。
{{</ notice >}} {{</ notice >}}

8
content/zh/docs/pluggable-components/auditing-logs.md
View File

@ -100,15 +100,15 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `auditing`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `auditing`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
auditing: auditing:
@ -150,8 +150,6 @@ KubeSphere 审计日志系统提供了一套与安全相关并按时间顺序排
验证您可以使用右下角**工具箱**中的**操作审计**功能。 验证您可以使用右下角**工具箱**中的**操作审计**功能。
![auditing-operating](/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/auditing-operating.png)
{{</ tab >}} {{</ tab >}}
{{< tab "通过 kubectl 验证组件的安装" >}} {{< tab "通过 kubectl 验证组件的安装" >}}

12
content/zh/docs/pluggable-components/devops.md
View File

@ -43,7 +43,7 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
### 在 Kubernetes 上安装 ### 在 Kubernetes 上安装
[在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用 DevOps（可选服务组件）。 [在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用 DevOps（可选系统组件）。
1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。 1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。
@ -70,15 +70,15 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台，点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`，点击搜索结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `devops`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `devops`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
devops: devops:
@ -102,9 +102,7 @@ DevOps 系统为用户提供了一个自动化的环境，应用可以自动发
{{< tab "在仪表板中验证组件的安装" >}} {{< tab "在仪表板中验证组件的安装" >}}
进入**服务组件**，检查 **DevOps** 的状态，可以看到如下类似图片： 进入**系统组件**，检查 **DevOps** 标签页中的所有组件都处于**健康**状态。
![devops](/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/devops.png)
{{</ tab >}} {{</ tab >}}

8
content/zh/docs/pluggable-components/events.md
View File

@ -102,17 +102,17 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `events`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `events`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
events: events:
@ -156,8 +156,6 @@ KubeSphere 事件系统使用户能够跟踪集群内部发生的事件，例如
验证您可以使用右下角**工具箱**中的**事件查询**功能。 验证您可以使用右下角**工具箱**中的**事件查询**功能。
![event-search](/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/event-search.png)
{{</ tab >}} {{</ tab >}}
{{< tab "通过 kubectl 验证组件的安装" >}} {{< tab "通过 kubectl 验证组件的安装" >}}

8
content/zh/docs/pluggable-components/kubeedge.md
View File

@ -77,10 +77,10 @@ KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上
1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。 1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。
2. 点击**自定义资源 CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。 2. 点击 **CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png" height="20px">，然后选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubeedge/three-dots.png" height="20px">，然后选择**编辑配置文件**。
@ -156,9 +156,7 @@ KubeEdge 的组件在两个单独的位置运行——云上和边缘节点上
{{< tab "在仪表板中验证组件的安装" >}} {{< tab "在仪表板中验证组件的安装" >}}
在**集群管理**页面，您可以看到**节点管理**下出现**边缘节点**板块。 在**集群管理**页面，您可以看到**节点**下出现**边缘节点**板块。
![edge-nodes](/images/docs/zh-cn/enable-pluggable-components/kubeedge/edge-nodes.png)
{{</ tab >}} {{</ tab >}}

12
content/zh/docs/pluggable-components/logging.md
View File

@ -61,7 +61,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
### 在 Kubernetes 上安装 ### 在 Kubernetes 上安装
[在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用日志系统（可选服务组件）。 [在 Kubernetes 上安装 KubeSphere](../../installing-on-kubernetes/introduction/overview/) 的教程中说明了在 Kubernetes 上安装 KubeSphere 的流程，不过，需要事先在 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件中启用日志系统（可选系统组件）。
1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。 1. 下载 [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.1.1/cluster-configuration.yaml) 文件，然后打开并开始编辑。
@ -104,17 +104,17 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/three-dots.png" height="20px">，选择**编辑配置文件**。
4. 在该 YAML 文件中，搜寻到 `logging`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**更新**，保存配置。 4. 在该 YAML 文件中，搜寻到 `logging`，将 `enabled` 的 `false` 改为 `true`。完成后，点击右下角的**确定**，保存配置。
```yaml ```yaml
logging: logging:
@ -155,9 +155,7 @@ KubeSphere 为日志收集、查询和管理提供了一个强大的、全面的
{{< tab "在仪表板中验证组件的安装" >}} {{< tab "在仪表板中验证组件的安装" >}}
进入**服务组件**，检查 **Logging** 的状态，可以看到如下类似图片： 进入**系统组件**，检查**日志**标签页中的所有组件都处于**健康**状态。
![logging](/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/logging.png)
{{</ tab >}} {{</ tab >}}

4
content/zh/docs/pluggable-components/metrics-server.md
View File

@ -70,11 +70,11 @@ KubeSphere 支持用于[部署](../../project-user-guide/application-workloads/d
1. 以 `admin` 身份登录控制台。点击左上角**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看详情页。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看详情页。
{{< notice info >}} {{< notice info >}}
自定义资源 (CRD) 能让用户创建新的资源类型，而无需添加其他 API 服务器。用户可以像其他原生 Kubernetes 对象一样使用这些资源。 定制资源定义（CRD）能让用户创建新的资源类型，而无需添加其他 API 服务器。用户可以像其他原生 Kubernetes 对象一样使用这些资源。
{{</ notice >}} {{</ notice >}}

8
content/zh/docs/pluggable-components/network-policy.md
View File

@ -77,10 +77,10 @@ weight: 6900
1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/enable-pluggable-components/network-policies/three-dots.png" height="20px">，选择**编辑配置文件**。
@ -106,6 +106,4 @@ weight: 6900
## 验证组件的安装 ## 验证组件的安装
如果您能在**网络管理**中看到**网络策略**，如下图所示，说明安装成功，因为安装组件之后才会显示这部分。 如果您能在**网络**中看到**网络策略**，说明安装成功，因为安装组件之后才会显示这部分。
![网络策略](/images/docs/zh-cn/enable-pluggable-components/network-policies/network-policy.PNG)

8
content/zh/docs/pluggable-components/pod-ip-pools.md
View File

@ -70,10 +70,10 @@ weight: 6920
1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。 1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。
2. 点击**自定义资源 CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。 2. 点击 **CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px">，然后选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/three-dots.png" height="20px">，然后选择**编辑配置文件**。
@ -99,6 +99,4 @@ weight: 6920
## 验证组件的安装 ## 验证组件的安装
在**集群管理**页面，您可以在**网络管理**下看到**容器组 IP 池**。 在**集群管理**页面，您可以在**网络**下看到**容器组 IP 池**。
![pod-ip-pool](/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/pod-ip-pool.png)

8
content/zh/docs/pluggable-components/service-mesh.md
View File

@ -68,10 +68,10 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。 1. 以 `admin` 身份登录控制台。点击左上角的**平台管理**，选择**集群管理**。
2. 点击**自定义资源 CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。 2. 点击 **CRD**，在搜索栏中输入 `clusterconfiguration`。点击结果查看其详细页面。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px">，选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/three-dots.png" height="20px">，选择**编辑配置文件**。
@ -100,9 +100,7 @@ KubeSphere 服务网格基于 [Istio](https://istio.io/)，将微服务治理和
{{< tab "在仪表板中验证组件的安装" >}} {{< tab "在仪表板中验证组件的安装" >}}
进入**服务组件**，查看 **Istio** 的状态。您可能会看到如下图所示的界面： 进入**系统组件**，检查 **Istio** 标签页中的所有组件都处于**健康**状态。
![istio](/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/istio.png)
{{</ tab >}} {{</ tab >}}

8
content/zh/docs/pluggable-components/service-topology.md
View File

@ -70,10 +70,10 @@ weight: 6915
1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。 1. 使用 `admin` 用户登录控制台。点击左上角的**平台管理**，然后选择**集群管理**。
2. 点击**自定义资源 CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。 2. 点击 **CRD**，然后在搜索栏中输入 `clusterconfiguration`。点击搜索结果查看其详情页。
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不新增 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png" height="20px">，然后选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的 <img src="/images/docs/zh-cn/enable-pluggable-components/service-topology/three-dots.png" height="20px">，然后选择**编辑配置文件**。
@ -103,9 +103,7 @@ weight: 6915
{{< tab "在仪表板中验证组件的安装" >}} {{< tab "在仪表板中验证组件的安装" >}}
进入一个项目中，导航到**应用负载**下的**服务**，即可看到**拓扑图**选项卡下**服务**的拓扑图。 进入一个项目中，导航到**应用负载**下的**服务**，即可看到**服务拓扑**页签下**服务**的拓扑图。
![topology1](/images/docs/zh-cn/enable-pluggable-components/service-topology/topology.png)
{{</ tab >}} {{</ tab >}}

2
content/zh/docs/project-user-guide/application/compose-app.md
View File

@ -21,7 +21,7 @@ weight: 10140
2. 设置应用名称（例如 `bookinfo`）并点击**下一步**。 2. 设置应用名称（例如 `bookinfo`）并点击**下一步**。
3. 在**服务组件**页面，您需要构建自制应用的微服务。点击**添加服务**，选择**无状态服务**。 3. 在**系统组件**页面，您需要构建自制应用的微服务。点击**添加服务**，选择**无状态服务**。
4. 设置服务名称（例如 `productpage`）并点击**下一步**。 4. 设置服务名称（例如 `productpage`）并点击**下一步**。

2
content/zh/docs/quick-start/all-in-one-on-linux.md
View File

@ -258,7 +258,7 @@ https://kubesphere.io 20xx-xx-xx xx:xx:xx
{{</ notice >}} {{</ notice >}}
登录至控制台后，您可以在**服务组件**中查看各个组件的状态。如果要使用相关服务，您可能需要等待部分组件启动并运行。您也可以使用 `kubectl get pod --all-namespaces` 来检查 KubeSphere 相关组件的运行状况。 登录至控制台后，您可以在**系统组件**中查看各个组件的状态。如果要使用相关服务，您可能需要等待部分组件启动并运行。您也可以使用 `kubectl get pod --all-namespaces` 来检查 KubeSphere 相关组件的运行状况。
![service-components](/images/docs/zh-cn/quickstart/all-in-one-on-linux/service-components.png) ![service-components](/images/docs/zh-cn/quickstart/all-in-one-on-linux/service-components.png)

8
content/zh/docs/quick-start/enable-pluggable-components.md
View File

@ -78,7 +78,7 @@ weight: 2600
kubectl apply -f cluster-configuration.yaml kubectl apply -f cluster-configuration.yaml
``` ```
无论是在 Linux 上还是在 Kubernetes 上安装 KubeSphere，安装后都可以在 KubeSphere 的 Web 控制台中检查已启用组件的状态。转到**服务组件**，可以看到类似如下图片： 无论是在 Linux 上还是在 Kubernetes 上安装 KubeSphere，安装后都可以在 KubeSphere 的 Web 控制台中检查已启用组件的状态。转到**系统组件**，可以看到类似如下图片：
![服务组件](/images/docs/zh-cn/quickstart/enable-pluggable-components/服务组件.jpg) ![服务组件](/images/docs/zh-cn/quickstart/enable-pluggable-components/服务组件.jpg)
@ -96,12 +96,12 @@ weight: 2600
![集群管理](/images/docs/zh-cn/quickstart/enable-pluggable-components/集群管理.png) ![集群管理](/images/docs/zh-cn/quickstart/enable-pluggable-components/集群管理.png)
2. 点击**自定义资源 CRD**，然后在搜索栏中输入 `clusterconfiguration`，点击搜索结果进入其详情页面。 2. 点击 **CRD**，然后在搜索栏中输入 `clusterconfiguration`，点击搜索结果进入其详情页面。
![CRD](/images/docs/zh-cn/quickstart/enable-pluggable-components/CRD.png) ![CRD](/images/docs/zh-cn/quickstart/enable-pluggable-components/CRD.png)
{{< notice info >}} {{< notice info >}}
自定义资源定义 (CRD) 允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些自定义资源。 定制资源定义（CRD）允许用户在不增加额外 API 服务器的情况下创建一种新的资源类型，用户可以像使用其他 Kubernetes 原生对象一样使用这些定制资源。
{{</ notice >}} {{</ notice >}}
3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑配置文件**。 3. 在**资源列表**中，点击 `ks-installer` 右侧的三个点，然后选择**编辑配置文件**。
@ -146,7 +146,7 @@ weight: 2600
##################################################### #####################################################
``` ```
7. 登录 KubeSphere 控制台，在**服务组件**中可以查看不同组件的状态。 7. 登录 KubeSphere 控制台，在**系统组件**中可以查看不同组件的状态。
![服务组件](/images/docs/zh-cn/quickstart/enable-pluggable-components/服务组件.jpg) ![服务组件](/images/docs/zh-cn/quickstart/enable-pluggable-components/服务组件.jpg)

2
content/zh/docs/quick-start/minimal-kubesphere-on-k8s.md
View File

@ -47,7 +47,7 @@ weight: 2200
4. 确保在安全组中打开了端口 `30880`，并通过 NodePort `(IP:30880)` 使用默认帐户和密码 `(admin/P@88w0rd)` 访问 Web 控制台。 4. 确保在安全组中打开了端口 `30880`，并通过 NodePort `(IP:30880)` 使用默认帐户和密码 `(admin/P@88w0rd)` 访问 Web 控制台。
5. 登录控制台后，您可以在**服务组件**中检查不同组件的状态。如果要使用相关服务，可能需要等待某些组件启动并运行。 5. 登录控制台后，您可以在**系统组件**中检查不同组件的状态。如果要使用相关服务，可能需要等待某些组件启动并运行。
![kubesphere-components](/images/docs/zh-cn/quickstart/minimal-kubesphere-on-k8s/kubesphere-components.png) ![kubesphere-components](/images/docs/zh-cn/quickstart/minimal-kubesphere-on-k8s/kubesphere-components.png)

2
content/zh/docs/quick-start/wordpress-deployment.md
View File

@ -78,7 +78,7 @@ WordPress（使用 PHP 语言编写）是免费、开源的内容管理系统，
![basic-info](/images/docs/zh-cn/quickstart/wordpress-deployment/basic-info.png) ![basic-info](/images/docs/zh-cn/quickstart/wordpress-deployment/basic-info.png)
3. 在**服务组件**中，点击**添加服务**以在应用中设置组件。 3. 在**系统组件**中，点击**添加服务**以在应用中设置组件。
![add-service](/images/docs/zh-cn/quickstart/wordpress-deployment/add-service.png) ![add-service](/images/docs/zh-cn/quickstart/wordpress-deployment/add-service.png)

2
content/zh/docs/toolbox/auditing/auditing-receive-customize.md
View File

@ -126,7 +126,7 @@ spec:
``` ```
{{< notice tip >}} {{< notice tip >}}
您也可以使用拥有 `platform-admin` 角色的帐户登录控制台，在**集群管理**页面转到**自定义资源 CRD**，搜索 `Webhook`，直接编辑 `kube-auditing-webhook`。 您也可以使用拥有 `platform-admin` 角色的帐户登录控制台，在**集群管理**页面转到 **CRD**，搜索 `Webhook`，直接编辑 `kube-auditing-webhook`。
{{</ notice >}} {{</ notice >}}

2
content/zh/docs/toolbox/auditing/auditing-rule.md
View File

@ -8,7 +8,7 @@ weight: 15320
审计规则定义了处理审计日志的策略。KubeSphere 审计日志为用户提供两种 CRD 规则（`archiving-rule` 和 `alerting-rule`）以供自定义。 审计规则定义了处理审计日志的策略。KubeSphere 审计日志为用户提供两种 CRD 规则（`archiving-rule` 和 `alerting-rule`）以供自定义。
启用 [KubeSphere 审计日志](../../../pluggable-components/auditing-logs/)后，使用拥有 `platform-admin` 角色的帐户登录控制台。在**集群管理**页面转到**自定义资源 CRD**，在搜索栏中输入 `rules.auditing.kubesphere.io`。点击搜索结果 **Rule**，您便可以看到这两种 CRD 规则，如下所示。 启用 [KubeSphere 审计日志](../../../pluggable-components/auditing-logs/)后，使用拥有 `platform-admin` 角色的帐户登录控制台。在**集群管理**页面转到 **CRD**，在搜索栏中输入 `rules.auditing.kubesphere.io`。点击搜索结果 **Rule**，您便可以看到这两种 CRD 规则，如下所示。
![审计 CRD](/images/docs/zh-cn/toolbox/auditing/auditing-rules/auditing-crd.PNG) ![审计 CRD](/images/docs/zh-cn/toolbox/auditing/auditing-rules/auditing-crd.PNG)

4
content/zh/live/uisee0923-live.md
View File

@ -1,6 +1,6 @@
--- ---
title: Kubebuilder 使用简介 title: Kubebuilder 使用简介
description: Kubebuilder 是一个帮助快速开发自定义资源及控制器的框架工具。和大家一起走进 Kubebuilder，初步了解 Kubebuilder 的基本原理以及使用方法。 description: Kubebuilder 是一个帮助快速开发定制资源及控制器的框架工具。和大家一起走进 Kubebuilder，初步了解 Kubebuilder 的基本原理以及使用方法。
keywords: KubeSphere, Kubernetes, Kuberbuilder keywords: KubeSphere, Kubernetes, Kuberbuilder
css: scss/live-detail.scss css: scss/live-detail.scss
@ -15,7 +15,7 @@ section1:
--- ---
## 分享内容简介 ## 分享内容简介
Kubebuilder 是一个帮助快速开发自定义资源及控制器的框架工具。本次分享基于上一讲 [Kubernetes 控制器原理简介](https://kubesphere.com.cn/live/uisee0916-live/)，和大家一起走进 Kubebuilder，初步了解 Kubebuilder 的基本原理以及使用方法。 Kubebuilder 是一个帮助快速开发定制资源及控制器的框架工具。本次分享基于上一讲 [Kubernetes 控制器原理简介](https://kubesphere.com.cn/live/uisee0916-live/)，和大家一起走进 Kubebuilder，初步了解 Kubebuilder 的基本原理以及使用方法。
## 讲师简介 ## 讲师简介

2
localization_style_guides/KubeSphere Localization Style Guide (for Simplified Chinese).md
View File

@ -18,7 +18,7 @@ Make sure the term you use is the correct one in UI, or it may confuse readers w
| Source Text | Correct Target Text | Wrong Target Text | | Source Text | Correct Target Text | Wrong Target Text |
| -------------------------------------------------------- | ------------------------------------ | -------------------------------- | | -------------------------------------------------------- | ------------------------------------ | -------------------------------- |
| Click **Components** on the **Cluster Management** page. | 在**集群管理**页面点击**服务组件**。 | 在**集群管理**页面点击**组件**。 | | Click **System Components** on the **Cluster Management** page. | 在**集群管理**页面点击**系统组件**。 | 在**集群管理**页面点击**系统组件**。 |
## Format ## Format

BIN
static/images/docs/enable-pluggable-components/kubeedge/edge-nodes.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 64 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-alerting/alerting-section.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 76 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-app-store/app-store.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 867 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-auditing-logs/auditing-operating.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 77 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-devops-system/devops.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 117 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-events/event-search.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 70 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-logging-system/logging.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 105 KiB

BIN
static/images/docs/enable-pluggable-components/kubesphere-service-mesh/istio.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 143 KiB

BIN
static/images/docs/enable-pluggable-components/network-policies/networkpolicy.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 78 KiB

BIN
static/images/docs/enable-pluggable-components/pod-ip-pools/pod-ip-pool.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 68 KiB

BIN
static/images/docs/enable-pluggable-components/service-topology/topology.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 114 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubeedge/edge-nodes.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 115 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-alerting/alerting-section.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 141 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-app-store/app-store-page.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 366 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-auditing-logs/auditing-operating.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 72 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-devops-system/devops.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 121 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-events/event-search.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 69 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-logging-system/logging.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 105 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/kubesphere-service-mesh/istio.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 151 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/network-policies/network-policy.PNG
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 83 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/pod-ip-pools/pod-ip-pool.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 122 KiB

BIN
static/images/docs/zh-cn/enable-pluggable-components/service-topology/topology.png
View File

Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 223 KiB