- 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
Show all
Copied.
Comparison Among Basic and Community Editions
Category |
Function |
Item |
Community Edition |
Basic Edition |
---|---|---|---|---|
Specification |
Management scale |
Maximum number of pods a mesh can manage. |
- |
200 |
Basic functions |
Service discovery and registration |
The service center cluster obtains the service list, automatically registers containerized services, and refreshes service pod statuses. You do not need to implement the registration and subscription logic as services can be automatically discovered, and dynamically managed. |
√ |
√ |
Multiple service versions |
Supports version-based service management and monitoring. |
- |
√ |
|
Supports version-based service workload management. |
√ |
√ |
||
Multiple service ports |
Supports multi-port, multi-protocol service management. |
√ |
√ |
|
Supports multi-port grayscale release. |
- |
√ |
||
Multiple service types |
Supports containerized service backend. |
√ |
√ |
|
Protocols and languages |
HTTP and gRPC grayscale release, governance, and monitoring (varying with protocols), language- and framework-agnostic, and non-intrusive |
√ |
√ |
|
Application gateway |
Supports layer-4 and layer-7 external access, entry path mapping, TLS termination at gateways, and configuration of external certificates and secrets. |
√ |
√ |
|
Load balancing |
Supports round robin, random, minimum number of connections, and consistent hashing algorithms based on a specific HTTP header or cookie value. |
√ |
√ |
|
Fault injection |
Supports injection of faults with a specified delay or error and configuration of fault percentage. |
√ |
√ |
|
Outlier detection |
Supports layer-7 request management, including the maximum number of requests, maximum number of requests per connection, maximum number of queued requests, and maximum number of retries; layer-4 connection management, including the maximum number of connections and connection timeout interval; exception check, and automatic isolation and recovery of faulty pods. |
√ |
√ |
|
Traffic types |
Supports governance of internal communication between services and external access to services (ingress traffic). |
√ |
√ |
|
Running environments |
Supports containerized application management. |
√ |
√ |
|
Authentication |
Supports non-intrusive two-way TLS authentication and channel encryption. |
√ |
√ |
|
Authorization |
Supports service access authorization management. |
√ |
√ |
|
Grayscale release |
Supports grayscale traffic distribution policies based on the browser, operating system, custom HTTP header, cookie content, and URL; and grayscale release based on request parameters and traffic ratio. |
√ |
√ |
|
Supports canary release template. |
- |
√ |
||
Supports blue-green deployment template. |
- |
√ |
||
Supports monitoring of service status during grayscale release to facilitate decision making. |
- |
√ |
||
Supports monitoring of service requests during grayscale release to facilitate decision making. |
- |
√ |
||
Supports dynamic configuration of the number of service pods during grayscale release. |
- |
√ |
||
Supports dynamic traffic ratio monitoring during grayscale release. |
- |
√ |
||
Application topology |
Provides global topology of traces in applications. |
- |
√ |
|
Provides key metrics such as the number of total requests and abnormal requests in topology. |
- |
√ |
||
Supports real-time application topology. |
- |
√ |
||
Tracing |
Supports non-intrusive tracing point setting. |
√ |
√ |
|
Monitoring metrics |
Supports monitoring of the running data of service pod CPUs, memory, and disks, monitoring of access metrics such as RPS and latency, analyzing statistics of access and abnormal metrics, interconnection with open source metric components such as Prometheus, and interconnection with different metric backends. |
√ |
√ |
|
Access logs |
Supports non-intrusive collection of access logs. |
√ |
√ |
|
Installation |
Supports enabling Istio for existing and newly created Kubernetes clusters in a few clicks. |
- |
√ |
|
Upgrade |
Supports smooth upgrade of the control plane without interrupting application services. |
√ |
√ |
|
Supports smooth upgrade of the data plane without interrupting application services. |
√ |
√ |
||
Add-on management |
Supports installation of community add-ons, such as Grafana and Prometheus in a few clicks. |
- |
√ |
|
Supports installation of Tracing in a few clicks. |
- |
√ |
||
Supports installation of Kiali in a few clicks. |
- |
√ |
||
Supports installation of ELK in a few clicks. |
- |
√ |
||
Agent management |
Supports transparent and iptables-based traffic interception, as well as automatic proxy injection at namespace and workload levels. |
√ |
√ |
|
Proxy mode |
Supports a sidecar in each pod. |
√ |
√ |
|
Command line tool |
Supports traffic policy management using command line tools, such as istioctl and kubectl. |
- |
√ |
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