Creating a Service Mesh¶
ASM allows you to create a Basic service mesh for commercial use.
Prerequisites¶
A CCE cluster is available.
Constraints¶
ASM depends on the domain name resolution of CoreDNS. Before creating a service mesh for a cluster, ensure that the cluster has required resources and CoreDNS is running normally.
Istio components v1.13 and v1.15 cannot run on nodes running CentOS or EulerOS 2.5. When creating a service mesh, do not specify these types of nodes as master nodes.
Procedure¶
Log in to the ASM console.
Click Create Mesh in the upper right corner.
Configure the following parameters.
Mesh Edition
Only service meshes of the Basic edition are supported for commercial use.
Mesh Name
Enter a service mesh name, which consists of 4 to 64 characters. It must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.
Service mesh names under the same account must be unique and cannot be modified after creation.
Istio Version
Select the Istio version supported by the service mesh.
Enable IPv6
Conditions for enabling IPv4/IPv6 dual stack for a service mesh
Service Mesh Edition
Istio Version
Cluster Type
Cluster Network Type
Remarks
Basic edition
1.18 or later
CCE Turbo clusters
Cloud native network 2.0
To enable IPv6.
For details, see How Do I Create a Service Mesh with IPv4/IPv6 Dual Stack Enabled
Note
Enable IPv6 is only available in Basic service meshes based on Istio 1.18 or later.
IPv4/IPv6 dual stack cannot be enabled for a service mesh whose Istio version is upgraded to 1.18 or later.
IPv4/IPv6 dual stack cannot be disabled once it is enabled for a service mesh. IPv4/IPv6 dual stack cannot be enabled for an existing service mesh.
Cluster
Select the cluster from the cluster list or enter the cluster name in the upper right corner of the list to search for it. You can only select the clusters whose versions are supported by the current service mesh version.
Mesh Control Plane Node
The control plane components of the Basic service mesh are installed in the user cluster. Therefore, you need to select a node for installing the control plane. If HA is required, you can select two or more nodes from different AZs.
A selected node will be labeled with istio:master, and the components will be scheduled to that node.
Observability Configuration
Application Metrics
If this option is enabled, you can specify service access metrics, application topologies, and service health and SLO definitions in the service mesh.
Tracing
Sampling Rate: Number of requests generated by the tracing service/Total number of requests
Version: tracing service. If you select Third-party Jaeger/Zipkin service, you need to set Service Address and Service Port, which indicate the address and port number used by the third-party tracing service to receive requests.
Note
Only Istio 1.15 or later support the third-party tracing service.
If you want to use the third-party Jaeger or Zipkin service, install it first. Then, obtain the service address.
The default service ports of Jaeger and Zipkin are both 9411. If you customize the service port during Jaeger or Zipkin installation, replace Service Port with the actual value.
(Optional) Configure advanced settings.
Namespace Injection Settings
Select a namespace and label it with istio-injection=enabled. After being restarted, all pods in the namespace will be automatically injected with an istio-proxy sidecar.
You can inject a sidecar in Mesh Configuration > Sidecar Management after the mesh is created. For details, see Injecting a Sidecar.
Restart Existing Services
: Pods of the existing services in the namespace will be restarted, which will temporarily interrupt your services. The istio-proxy sidecar is automatically injected into the pods of the existing services.
: The istio-proxy sidecar cannot be automatically injected into the pods of the existing services. You need to manually restart the workloads on the CCE console to inject the sidecar.Traffic Interception Settings
Note
By default, sidecars intercept all inbound and outbound traffic of pods. You can modify the default traffic rules in Traffic Interception Settings.
Inbound Ports: Inbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for inbound traffic redirection.
Include only specified ports means that the traffic to services in a service mesh over specified ports will be redirected to the sidecar.
Exclude only specified ports means that the traffic to services in a service mesh over the ports except the specified ports will be redirected to the sidecar.
Outbound Ports: Outbound ports separated by commas (,). You can use this field to specify the ports that will be included or excluded for outbound traffic redirection.
Include only specified ports means that the traffic from services in a service mesh over specified ports will be redirected to the sidecar.
Exclude only specified ports means that the traffic from services in a service mesh over the ports except the specified ports will be redirected to the sidecar.
Outbound IP Ranges: IP address ranges separated by commas (,) in CIDR format. You can use this field to specify the IP ranges that will be included or excluded for outbound traffic redirection.
Include only specified IP ranges means that the traffic from specified IP ranges will be redirected to the sidecar.
Exclude only specified IP ranges means that the traffic from IP ranges except the specified IP ranges will be redirected to the sidecar.
Resource Tags
Enter the tag key and tag value. A maximum of 20 tags can be added.
Review the service mesh configuration in Configuration List on the right of the page and click Submit.
It takes about 1 to 3 minutes to create a service mesh. If the service mesh status changes from Installing to Running, the service mesh is successfully created.
Note
When the service mesh is enabled, the following operations are performed:
Helm orchestrates the application into a Release as the resource of the service mesh control plane.