mirror of https://github.com/status-im/consul.git
/docs/connect/l7-traffic
This commit is contained in:
parent
4b6fef4c97
commit
df9702f9d1
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Discovery Chain
|
||||
page_title: Service Mesh Traffic Management: Discovery Chain
|
||||
description: >-
|
||||
The service discovery process can be modeled as a "discovery chain" which
|
||||
passes through three distinct stages: routing, splitting, and resolution. Each
|
||||
of these stages is controlled by a set of configuration entries.
|
||||
Discovery chains compile service routing, splitting, and resolution configuration entries to direct traffic to specific instances in a service mesh. Learn about compiled discovery chain results, including discovery graph nodes and targets.
|
||||
---
|
||||
|
||||
# Discovery Chain
|
||||
# Discovery Chain for Service Mesh Traffic Management
|
||||
|
||||
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
|
||||
|
||||
|
|
|
@ -1,14 +1,13 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Connect - L7 Traffic Management
|
||||
page_title: Service Mesh Traffic Management: Overview
|
||||
description: >-
|
||||
Layer 7 traffic management allows operators to divide L7 traffic between
|
||||
different subsets of service instances when using Connect.
|
||||
Consul can route, split, and resolve Layer 7 traffic in a service mesh to support workflows like canary testing and blue/green deployments. Learn about the three config entry kind that define L7 traffic management behavior in Consul.
|
||||
---
|
||||
|
||||
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
|
||||
|
||||
# L7 Traffic Management
|
||||
# Service Mesh Traffic Management Overview
|
||||
|
||||
Layer 7 traffic management allows operators to divide L7 traffic between
|
||||
different
|
||||
|
|
Loading…
Reference in New Issue