Alibaba Cloud Service Mesh
Alibaba Cloud Service Mesh
Announcements and Updates
Historical release notes (before 2023)
Announcement on product changes
Announcement on the launch of commercial editions
CVE vulnerability fixes
What is ASM?
Functions and features
Support for Istio versions
Create an ASM instance
Add a cluster to an ASM instance
Create an ingress gateway service
Deploy an application in an ASM instance
Use Istio resources to route traffic to different versions of a service
Use Mesh Topology to view the topology of an application
Grant permissions to RAM users
service mesh product authorization
Manage global namespaces
Diagnose ASM instances
Enable Multi-Buffer for TLS acceleration
Roll back an Istio resource to an earlier version
Cluster And Workload Management
Plan CIDR blocks for multiple clusters on the data plane
Use ASM to manage applications in ASK clusters
Use ASM to manage applications in ECI pods running on virtual nodes of ACK clusters
Use ASM to manage applications in registered external Kubernetes clusters
Use ASM to manage applications in ACK edge clusters
Use ASM to deploy an application in multiple clusters in the same VPC
Use ASM to implement cross-region disaster recovery and load balancing
Configure redirection of HTTP or TCP health check requests for applications in an ASM instance
Install a sidecar proxy
Upgrade sidecar proxies
Enable automatic sidecar injection by using multiple methods
Configure namespace-level sidecar proxies
Configure a sidecar proxy by adding resource annotations
Configure settings to allow traffic to bypass sidecar proxies
Use the DNS proxy feature in an ASM instance
Write WASM filters for Envoy and deploy them in ASM
Use ORAS to simplify Wasm-based ASM instance extension
Enable a CNI plug-in to improve security
Configure sidecar parameters to balance HTTP/2 streaming performance and resource usage
Overview of ASM gateways
Manage Istio gateways
Advanced features of gateways
Integrate with existing systems
Use ASM to build distributed systems with fault tolerance capabilities
Use ASM to achieve gRPC load balancing
Use ASM to route traffic based on the locality
Access external services from an ASM instance
Access services over WebSocket connections in ASM
Use delegates to configure virtual services in an ASM instance
Implement end-to-end canary release based on lanes
Configure local throttling in ASM
Traffic labeling and label-based routing
Use an ASMAdaptiveConcurrency to implement adaptive concurrency control
Manage Spring Cloud services
Enable the Intra-zone Provider First feature
Use the warm-up feature
Preserve the source IP address of a client when the client accesses services in ASM
Use traffic mirroring for services within a cluster
Use Argo CD to implement end-to-end canary releases of application services
Metric monitoring and SLO management
Overview of zero trust security
Improve application security in ASM
Run an ASM authorization policy in trial mode
JWT authentication and authorization
ASM security policies
Namespace-level service access authorization
Enable plug-ins to extend ASM capabilities
Manage Envoy filters
Configuration Push Optimization
Configuration push optimization overview
Use service discovery selectors to improve the configuration push efficiency of the control plane
Use adaptive xDS optimization to improve the configuration push efficiency of the control plane
Use the sidecars that are automatically recommended based on access log analysis
Effects of sidecar recommendation on configuration push optimization
Integrate Argo CD with ASM to implement GitOps
Integrate ASM with Argo Rollouts to implement canary releases
Integrate Knative Serving autoscaling and traffic splitting to an ASM instance
Integrate cloud-native inference service KServe with ASM
Integrate an ALB instance with an ingress gateway
Use Flagger in ASM
List of operations by function
Make API requests
Create an AccessKey pair
End-to-end canary release
Use an SDK to manage Istio resources
Use the proxyless service mesh feature in gRPC services
Connection to a Service Registry
What is the difference between namespaces in an ASM instance and those of the clusters in the data plane managed by the ASM instance?
How do I specify the protocol of a service in a standard manner?
How do I delete a namespace in the terminating state?
What can I do if the pods of a Kubernetes cluster on the data plane cannot access the IP address of the SLB instance that is configured in an ingress gateway?
How can I retain the SLB instance configured for an ASM gateway when I delete the ASM gateway?
Why does the service authentication fail when business services in an ASM instance can access external databases?
Why are no gateways or non-Istio gateways returned when I run the kubectl command to query gateways?
Why does a destination rule not take effect after it is defined?
Why is a pod in the init crash state after a sidecar proxy is injected into the pod?
Why is no valid health check information displayed after sidecar injection?
Why do time-consuming requests get lost or fail after a sidecar proxy is injected into a pod?
Why does the memory usage of sidecars keep increasing?
How can I expose a cluster application that listens to the localhost to other pods in the cluster?