KubeSphere Service Mesh

On the basis of Istio, KubeSphere Service Mesh visualizes microservices governance and traffic management. It features a powerful toolkit including circuit breaking, blue-green deployment, canary release, traffic mirroring, tracing, observability, and traffic control. Developers can easily get started with KubeSphere Service Mesh without any code hacking, which greatly reduces the learning curve of Istio. All features of KubeSphere Service Mesh are designed to meet users’ demand for their business.

For more information, see Grayscale Release.

Enable KubeSphere Service Mesh 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, you create a default file config-sample.yaml. Modify the file by executing the following command:

    1. vi config-sample.yaml

    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 the following section to see how KubeSphere Service Mesh can be installed after installation.

  2. In this file, navigate to servicemesh and change false to true for enabled. Save the file after you finish.

    1. servicemesh:
    2. enabled: true # Change “false” to “true”.
    3. istio: # Customizing the istio installation configuration, refer to https://istio.io/latest/docs/setup/additional-setup/customize-installation/
    4.   components:
    5.     ingressGateways:
    6.     - name: istio-ingressgateway # Used to expose a service outside of the service mesh using an Istio Gateway. The value is false by defalut.
    7.       enabled: false
    8.     cni:
    9.       enabled: false # When the value is true, it identifies user application pods with sidecars requiring traffic redirection and sets this up in the Kubernetes pod lifecycle’s network setup phase.

    Note

  3. Run the following command to create a cluster using the configuration file:

    1. ./kk create cluster -f config-sample.yaml

Installing on Kubernetes

As you install KubeSphere on Kubernetes, you can enable KubeSphere Service Mesh first in the cluster-configuration.yaml file.

  1. Download the file cluster-configuration.yaml and edit it.

    1. vi cluster-configuration.yaml

  2. In this local cluster-configuration.yaml file, navigate to servicemesh and enable it by changing false to true for enabled. Save the file after you finish.

    1. servicemesh:
    2. enabled: true # Change “false” to “true”.
    3. istio: # Customizing the istio installation configuration, refer to https://istio.io/latest/docs/setup/additional-setup/customize-installation/
    4.   components:
    5.     ingressGateways:
    6.     - name: istio-ingressgateway # Used to expose a service outside of the service mesh using an Istio Gateway. The value is false by defalut.
    7.       enabled: false
    8.     cni:
    9.       enabled: false # When the value is true, it identifies user application pods with sidecars requiring traffic redirection and sets this up in the Kubernetes pod lifecycle’s network setup phase.

  3. Run the following commands to start installation:

    1. kubectl apply -f https://github.com/kubesphere/ks-installer/releases/download/v3.3.0/kubesphere-installer.yaml
    3. kubectl apply -f cluster-configuration.yaml

Enable KubeSphere Service Mesh After Installation

  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.

    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.

  3. In Custom Resources, click KubeSphere Service Mesh - 图1 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 OK in the lower-right corner to save the configuration.

    1. servicemesh:
    2. enabled: true # Change “false” to “true”.
    3. istio: # Customizing the istio installation configuration, refer to https://istio.io/latest/docs/setup/additional-setup/customize-installation/
    4.   components:
    5.     ingressGateways:
    6.     - name: istio-ingressgateway # Used to expose a service outside of the service mesh using an Istio Gateway. The value is false by defalut.
    7.       enabled: false
    8.     cni:
    9.       enabled: false # When the value is true, it identifies user application pods with sidecars requiring traffic redirection and sets this up in the Kubernetes pod lifecycle’s network setup phase.

  5. Run the following command in kubectl to check the installation process:

    1. kubectl logs -n kubesphere-system $(kubectl get pod -n kubesphere-system -l 'app in (ks-install, ks-installer)' -o jsonpath='{.items[0].metadata.name}') -f

    Note

    You can find the web kubectl tool by clicking KubeSphere Service Mesh - 图2 in the lower-right corner of the console.

Verify the Installation of the Component

Go to System Components and check whether all components on the Istio tab page is in Healthy state. If yes, the component is successfully installed.

Run the following command to check the status of Pods:

  1. kubectl get pod -n istio-system

The following is an example of the output if the component runs successfully:

  1. NAME                                    READY   STATUS    RESTARTS   AGE
  2. istio-ingressgateway-78dbc5fbfd-f4cwt   1/1     Running   0          9m5s
  3. istiod-1-6-10-7db56f875b-mbj5p          1/1     Running   0          10m
  4. jaeger-collector-76bf54b467-k8blr       1/1     Running   0          6m48s
  5. jaeger-operator-7559f9d455-89hqm        1/1     Running   0          7m
  6. jaeger-query-b478c5655-4lzrn            2/2     Running   0          6m48s
  7. kiali-f9f7d6f9f-gfsfl                   1/1     Running   0          4m1s
  8. kiali-operator-7d5dc9d766-qpkb6         1/1     Running   0          6m53s