KubeSphere Service Mesh
For more information, see Grayscale Release.
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 , you create a default file . Modify the file by executing the following command:
Note
If you adopt All-in-One Installation, 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 KubeSphere Service Mesh in this mode (for example, for testing purposes), refer to to see how KubeSphere Service Mesh can be installed after installation.In this file, navigate to
servicemesh
and changefalse
totrue
forenabled
. Save the file after you finish.servicemesh:
Create a cluster using the configuration file:
./kk create cluster -f config-sample.yaml
Installing on Kubernetes
Download the file and edit it.
In this local file, navigate to
servicemesh
and enable it by changingfalse
totrue
forenabled
. Save the file after you finish.servicemesh:
enabled: true # Change "false" to "true".
Execute the following commands to start installation:
kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.2.0/kubesphere-installer.yaml
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
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 this YAML file, navigate to
servicemesh
and changefalse
totrue
forenabled
. 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:
kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l app=ks-install -o jsonpath='{.items[0].metadata.name}') -f
Note
You can find the web kubectl tool by clicking in the lower-right corner of the console.
Go to System Components and check that all components on the Istio tab page is in Healthy state.
Execute the following command to check the status of Pods:
The output may look as follows if the component runs successfully: