Add installing on linux part for components

Signed-off-by: Sherlock113 <sherlockxu@yunify.com>

content/en/docs/pluggable-components/kubeedge.md

@@ -18,6 +18,35 @@ After you enable KubeEdge, you can [add edge nodes to your cluster](../../instal
 
 ## Enable KubeEdge before Installation
 
+### Installing on Linux
+
+When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
+
+1. In the tutorial of [Installing KubeSphere on Linux](../../installing-on-linux/introduction/multioverview/), you create a default file `config-sample.yaml`. Modify the file by executing the following command:
+
+   ```bash
+   vi config-sample.yaml
+   ```
+
+   {{< notice note >}}
+   If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/), you do not need to create a `config-sample.yaml` file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable KubeEdge in this mode (e.g. for testing purposes), refer to [the following section](#enable-kubeedge-after-installation) to see how KubeEdge can be installed after installation.
+   {{</ notice >}}
+
+2. In this file, navigate to `kubeedge.enabled` and change `false` to `true`.
+
+   ```yaml
+   kubeedge:
+     enabled: true # Change "false" to "true".
+   ```
+
+3. 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. Save the file when you finish editing.
+
+4. Create a cluster using the configuration file:
+
+   ```bash
+   ./kk create cluster -f config-sample.yaml
+   ```
+
 ### Installing on Kubernetes
 
 As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introduction/overview/), you can enable KubeEdge first in the [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.0.0/cluster-configuration.yaml) file.

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

@@ -12,6 +12,34 @@ A Pod IP Pool is used to manage the Pod network address space, and the address s
 
 ## Enable Pod IP Pools before Installation
 
+### Installing on Linux
+
+When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
+
+1. In the tutorial of [Installing KubeSphere on Linux](../../installing-on-linux/introduction/multioverview/), you create a default file `config-sample.yaml`. Modify the file by executing the following command:
+
+   ```bash
+   vi config-sample.yaml
+   ```
+
+   {{< notice note >}}
+   If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/), you do not need to create a `config-sample.yaml` file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable Pod IP Pools in this mode (e.g. for testing purposes), refer to [the following section](#enable-pod-ip-pools-after-installation) to see how Pod IP Pools can be installed after installation.
+   {{</ notice >}}
+
+2. In this file, navigate to `network.ippool.type` and change `none` to `calico`. Save the file after you finish.
+
+   ```yaml
+   network:
+     ippool:
+       type: calico # Change "none" to "calico"
+   ```
+
+3. Create a cluster using the configuration file:
+
+   ```bash
+   ./kk create cluster -f config-sample.yaml
+   ```
+
 ### Installing on Kubernetes
 
 As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introduction/overview/), you can enable Pod IP Pools first in the [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.0.0/cluster-configuration.yaml) file.

content/en/docs/pluggable-components/service-topology.md

@@ -12,6 +12,34 @@ You can enable Service Topology to integrate [Weave Scope](https://www.weave.wor
 
 ## Enable Service Topology before Installation
 
+### Installing on Linux
+
+When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
+
+1. In the tutorial of [Installing KubeSphere on Linux](../../installing-on-linux/introduction/multioverview/), you create a default file `config-sample.yaml`. Modify the file by executing the following command:
+
+   ```bash
+   vi config-sample.yaml
+   ```
+
+   {{< notice note >}}
+   If you adopt [All-in-One Installation](../../quick-start/all-in-one-on-linux/), you do not need to create a `config-sample.yaml` file as you can create a cluster directly. Generally, the all-in-one mode is for users who are new to KubeSphere and look to get familiar with the system. If you want to enable Service Topology in this mode (e.g. for testing purposes), refer to [the following section](#enable-service-topology-after-installation) to see how Service Topology can be installed after installation.
+   {{</ notice >}}
+
+2. In this file, navigate to `network.topology.type` and change `none` to `weave-scope`. Save the file after you finish.
+
+   ```yaml
+   network:
+     topology:
+       type: weave-scope # Change "none" to "weave-scope".
+   ```
+
+3. Create a cluster using the configuration file:
+
+   ```bash
+   ./kk create cluster -f config-sample.yaml
+   ```
+
 ### **Installing on Kubernetes**
 
 As you [install KubeSphere on Kubernetes](../../installing-on-kubernetes/introduction/overview/), you can enable Service Topology first in the [cluster-configuration.yaml](https://github.com/kubesphere/ks-installer/releases/download/v3.0.0/cluster-configuration.yaml) file.