@ -17,8 +17,6 @@ This topic provides an overview of the gateway features shipped with Consul. Gat
## Mesh Gateways
-> **1.6.0+:** This feature is available in Consul versions 1.6.0 and newer.
Mesh gateways enable service mesh traffic to be routed between different Consul datacenters and admin partitions. The datacenters or partitions can reside
in different clouds or runtime environments where general interconnectivity between all services in all datacenters
isn't feasible.
@ -37,8 +35,6 @@ Mesh gateways enable the following scenarios:
## API Gateways
-> **1.15.0+:** This feature is available in Consul versions 1.8.0 and newer.
API gateways enable network access, from outside a service mesh, to services running in a Consul service mesh. The
systems accessing the services in the mesh, may be within your organizational network or external to it. This type of
network traffic is commonly called _north-south_ network traffic because it refers to the flow of data into and out of
@ -60,8 +56,6 @@ Refer to the following documentation for information on how to configure and dep
## Ingress Gateways
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and newer.
<Note>
Ingress gateway is deprecated and will not be enhanced beyond its current capabilities. Ingress gateway is fully supported
@ -88,8 +82,6 @@ and the [ingress gateway tutorial](/consul/tutorials/developer-mesh/service-mesh
## Terminating Gateways
-> **1.8.0+:** This feature is available in Consul versions 1.8.0 and newer.
Terminating gateways enable connectivity within your organizational network from services in the Consul service mesh
to services outside the mesh.
Services outside the mesh do not have sidecar proxies or are not [integrated natively](/consul/docs/connect/native).
Jeff-Apple
1 year ago