- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
- How Do I Handle a Canary Upgrade Failure?
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- How Do I Inject a Sidecar for the Pod Created Using a Job or CronJob?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Preparations
Before creating a grayscale release task, complete the following preparations.
Creating a VPC
Virtual Private Cloud (VPC) provides a logically isolated, configurable, and manageable virtual network environment, improving resource security and simplifying network deployment.
- Log in to the VPC console.
- Click Create VPC in the upper right corner.
- Set the parameters as prompted and click Create Now.
Creating a Key Pair
Create a key pair for identity authentication upon remote node login.
- Log in to the Elastic Cloud Server (ECS) console.
- In the navigation pane, choose Key Pair. On the Key Pair page, click Create Key Pair in the upper right corner.
- Enter a key pair name and click OK.
- Manually or automatically download the private key file. The file name is the specified key pair name with a suffix of .pem. Securely store the private key file. In the dialog box displayed, click OK.
NOTE:
For security purposes, a key pair can be downloaded only once. Keep it secure to ensure successful login.
Creating a Load Balancer
A load balancer will be used as the external access entry of a service mesh, which will route the traffic to backend services.
- Log in to the Elastic Load Balance (ELB) console.
- Click Create Elastic Load Balancer in the upper right corner.
- VPC and Subnet: Select the VPC and subnet created in Creating a VPC, configure other parameters as prompted, and click Apply Now.
Creating a Cluster
- Log in to the Cloud Container Engine (CCE) console.
- In the navigation pane, choose Resource Management > Clusters. Then, click Create CCE Cluster in the upper right corner.
- On the Configure page, configure the following parameters and retain the default values for other parameters.
- Cluster Name: Enter a cluster name, for example, cluster-test.
- VPC and Subnet: Select the VPC and subnet created in Creating a VPC.
- Click Next: Create Node, configure the following parameters, and retain the default values for other parameters.
- Specifications: 4 vCPUs and 8 GB memory.
- Login Mode: Select the key pair created in Creating a Key Pair for identity authentication upon remote node login.
- Click Next: Install Add-on and select the add-ons to be installed in the Install Add-on step.
System resource add-on must be installed. Advanced functional add-on is optional.
- Click Next: Confirm. Read the product constraints and select I am aware of the above limitations. Review the configured parameters and specifications.
- Submit the order.
It takes about 6 to 10 minutes to create a cluster. You can click Back to Cluster List to perform other operations on the cluster or click Go to Cluster Events to view the cluster details.
(Optional) Creating a Namespace
- Log in to the CCE console.
- In the navigation pane, choose Resource Management > Namespaces. Then, click Create Namespace in the upper right corner.
- Enter the namespace name and select the created cluster.
- Click OK.
Creating a Workload and a Service
- Log in to the CCE console.
- Choose Workloads from the navigation pane, click the Deployments tab, click Create Deployment in the upper right corner.
- Create a workload and a Service by referring to CCE User Guide.
Creating a Service Mesh
- Log in to the ASM console and click Create Mesh.
- Set Mesh Name to asmtest, select the cluster named cluster-test created in Creating a Cluster, and select a node on which the Istio control plane is installed. Select two or more nodes in different AZs.
- Click Show Advanced Settings. In the Sidecar Configuration area, select the namespace named default and enable Restart Existing Services.
- Review the mesh configuration in the 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.
Diagnosing Configurations
ASM diagnoses all services in a managed cluster. Grayscale release can be performed only for services that are diagnosed as normal.
- Log in to the ASM console, click the service mesh name asmtest to access its details page.
- In the navigation pane on the left, choose Service Management, select Namespace: default from the drop-down list box, and view the Configuration Diagnosis Result of servicetest.
- If the Configuration Diagnosis Result is Abnormal, click Fix to fix the issues.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot