Consul Connect Gateways

Consul Connect supports four gateway types for traffic flowing into and out of the mesh: mesh gateways for cross-datacenter and cross-partition traffic, ingress gateways for North-South entry, terminating gateways for access to non-mesh services, and the Consul API Gateway implementing the Kubernetes Gateway API.

API entry from apis.yml

apis.yml Raw ↑
aid: consul-connect:consul-connect-gateways
name: Consul Connect Gateways
description: 'Consul Connect supports four gateway types for traffic flowing into and out of the mesh:
  mesh gateways for cross-datacenter and cross-partition traffic, ingress gateways for North-South entry,
  terminating gateways for access to non-mesh services, and the Consul API Gateway implementing the Kubernetes
  Gateway API.'
humanURL: https://developer.hashicorp.com/consul/docs/connect/gateways
baseURL: https://developer.hashicorp.com
tags:
- API Gateway
- Gateways
- Ingress
- Mesh Gateway
- Terminating Gateway
properties:
- type: Documentation
  url: https://developer.hashicorp.com/consul/docs/connect/gateways
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/gateways/mesh-gateway
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/gateways/ingress-gateway
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/gateways/terminating-gateway
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/api-gateway
x-features:
- Mesh gateways for WAN federation and partition crossing
- Ingress gateways for L4/L7 ingress with TLS
- Terminating gateways for non-mesh service access
- API Gateway implementing the Kubernetes Gateway API
x-useCases:
- Federate Consul across datacenters securely
- Expose mesh services to external clients with TLS
- Allow mesh services to call legacy non-mesh endpoints