mirror of
https://github.com/status-im/consul.git
synced 2025-02-07 19:35:35 +00:00
29 lines
1.7 KiB
Plaintext
29 lines
1.7 KiB
Plaintext
---
|
||
layout: docs
|
||
page_title: Consul API Gateway Overview
|
||
description: >-
|
||
Using Consul API gateway functionality
|
||
---
|
||
|
||
# Consul API Gateway Overview
|
||
|
||
This topic provides an overview of the Consul API Gateway.
|
||
|
||
## What is Consul API Gateway?
|
||
|
||
Consul API Gateway is an add-on for Consul that helps users control access to services running within a Consul service mesh. The API gateway enables external network clients to access applications and services running in a Consul datacenter. This type of network traffic is commonly referred to as "north-south" network traffic as it refers to the flow of data into and out of a specific environment. Requests from clients can also be forwarded based on path or request protocol.
|
||
|
||
Consul API Gateway solves the following primary use cases:
|
||
|
||
- **Controlling access at the point of entry**: Consul API Gateway allows users to set the protocols of external connection requests and provide clients with TLS certificates from trusted providers (e.g., Verisign, Let’s Encrypt).
|
||
- **Simplifying traffic management**: The Consul API Gateway can load balance requests across services and route traffic to the appropriate service by matching one or more criteria, such as hostname, path, header presence or value, and HTTP Method type (e.g., GET, POST, PATCH).
|
||
|
||
## Implementation
|
||
|
||
Consul API Gateway implements the Kubernetes [Gateway API Specification](https://gateway-api.sigs.k8s.io/). This specification defines a set of custom resource definitions (CRD) that can create logical gateways and routes based on the path or protocol of a client request.
|
||
|
||
## Additional Resources
|
||
|
||
You can learn more about using Consul API Gateway by completing the [Consul API Gateway tutorial](https://learn.hashicorp.com/tutorials/consul/kubernetes-api-gateway).
|
||
|