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 (e.g. 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.topology:
type: weave-scope # Change "none" to "weave-scope".
Create a cluster using the configuration file:
Installing on Kubernetes
As you install KubeSphere on Kubernetes, you can enable Service Topology first in the file.
In this local
cluster-configuration.yaml
file, navigate tonetwork.topology.type
and enable it by changingnone
toweave-scope
. Save the file after you finish.network:
topology:
Execute the following commands to start installation:
kubectl apply -f cluster-configuration.yaml
Log in to the console as
admin
. Click Platform in the top-left corner and select Cluster Management.Click CRDs and enter
clusterconfiguration
in the search bar. Click the result to view its detail page.Info
A Custom Resource Definition (CRD) allows users to create a new type of resources without adding another API server. They can use these resources like any other native Kubernetes objects.
In Resource List, click the three dots on the right of
ks-installer
and select Edit YAML.You can use the web kubectl to check the installation process by executing the following command:
Tip
You can find the web kubectl tool by clicking the hammer icon in the bottom-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 Topology tab.
Execute the following command to check the status of Pods:
kubectl get pod -n weave
The output may look as follows if the component runs successfully: