Service Topology
When you implement multi-node installation of KubeSphere on Linux, you need to create a configuration file, which lists all KubeSphere components.
In the tutorial of Installing KubeSphere on Linux, you create a default file . Modify the file by executing the following command:
Note
If you adopt , 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 (for example, for testing purposes), refer to the following section to see how Service Topology can be installed after installation.In this file, navigate to
network.topology.type
and changenone
toweave-scope
. Save the file after you finish.network:
type: weave-scope # Change "none" to "weave-scope".
Create a cluster using the configuration file:
./kk create cluster -f config-sample.yaml
Installing on Kubernetes
Download the file cluster-configuration.yaml and edit it.
In this local file, navigate to
network.topology.type
and enable it by changingnone
toweave-scope
. Save the file after you finish.network:
topology:
type: weave-scope # Change "none" to "weave-scope".
Log in to the console as
admin
. Click Platform in the upper-left corner and select Cluster Management.Click CRDs and enter
clusterconfiguration
in the search bar. Click the result to view its detail page.Info
In Custom Resources, click on the right of
ks-installer
and select Edit YAML.In this YAML file, navigate to
network
and changenetwork.topology.type
toweave-scope
. After you finish, click OK in the lower-right corner to save the configuration.You can use the web kubectl to check the installation process by executing the following command:
Note
You can find the web kubectl tool by clicking in the lower-right corner of the console.
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.
kubectl get pod -n weave
The output may look as follows if the component runs successfully: