The service-splitter config entry kind controls how to split incoming Connect requests across different subsets of a single service (like during staged canary rollouts), or perhaps across different services (like during a v2 rewrite or other type of codebase migration).
---
# Service Splitter <sup>(beta)</sup>
-> **1.6.0+:** This config entry is available in Consul versions 1.6.0 and newer.
# Service Splitter
The `service-splitter` config entry kind controls how to split incoming Connect
requests across different subsets of a single service (like during staged
A Mesh Gateway enables better routing of a Connect service's data to upstreams in other datacenters. This section details how to use Envoy and describes how you can plug in a gateway of your choice.
---
# Mesh Gateways <sup>(beta)</sup>
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
# Mesh Gateways
Mesh gateways enable routing of Connect traffic between different Consul datacenters. Those datacenters
can reside in different clouds or runtime environments where general interconnectivity between all services
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 Chain <sup>beta</sup>
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
# Discovery Chain
~> This topic is part of a [low-level API](/api/discovery-chain.html)
primarily targeted at developers building external [Connect proxy
<p><strong>1.6.0 beta Available:</strong> Read more about the new features coming in 1.6.0 in the
<a href="https://www.hashicorp.com/blog/hashicorp-consul-1-6">announcement post</a>. Binaries can be accessed on <a href="https://releases.hashicorp.com/consul/">releases.hashicorp.com</a>. View the <a href="https://github.com/hashicorp/consul/blob/v1.6.0-beta1/CHANGELOG.md">changelog</a> for details.
R.B. Boyer
5 years ago
committed by