Overview
Traffic governance is a core function of Istio. It provides you with non-intrusive traffic governance capabilities. You only need to focus on your own service logic rather than service access management. The problems to be solved by traffic governance are as follows:
- Dynamically modifying load balancing policies for cross-service access, such as configuring consistent hashing to forward traffic to specific service pods
- Distributing a certain proportion of traffic to a specific version of a service when the service has two online versions
- Protecting services, for example, limiting the number of concurrent connections and requests, and isolating faulty service pods
- Dynamically modifying the content of a service or simulating a service running fault
ASM supports traffic governance capabilities such as retry, timeout, connection pool, outlier detection, load balancing, HTTP header, and fault injection, meeting governance requirements in most service scenarios.
Mesh Function |
Governance Role |
|
Service Initiator |
Service Provider |
|
Route management |
● |
\ |
Load balancing |
● |
\ |
Tracing analysis |
● |
● |
Service authentication |
● |
● |
Observability data |
● |
● |
Retry |
● |
\ |
Rewriting |
● |
\ |
Redirection |
● |
\ |
Authorization |
\ |
● |
Fault injection |
● |
\ |
Constraints
Traffic governance cannot be performed for the service which configuration diagnosis fails. For details about fixing the issues, see Manual Fixing Items or Auto Fixing Items.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.