mirror of https://github.com/status-im/consul.git
Merge pull request #12416 from hashicorp/api-gateway-ga-docs
website: update API Gateway docs for v0.1.0 GA release
This commit is contained in:
Jeff-Apple
GitHub
commit
263357f7d5
|
|
@ -1,60 +1,45 @@
|
||||||
---
|
---
|
||||||
layout: docs
|
layout: docs
|
||||||
page_title: API Gateway
|
page_title: Consul API Gateway Usage
|
||||||
description: Using Consul API gateway functionality
|
description: >-
|
||||||
|
Using Consul API gateway functionality
|
||||||
---
|
---
|
||||||
|
|
||||||
# Consul API Gateway
|
# Consul API Gateway Usage
|
||||||
|
|
||||||
This topic describes how to use the Consul API Gateway add-on module, which 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.
|
This topic describes how to use the Consul API Gateway add-on module. It includes instructions for installation and configuration.
|
||||||
|
|
||||||
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).
|
|
||||||
|
|
||||||
## Introduction
|
|
||||||
|
|
||||||
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. Consul API Gateway solves two 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).
|
|
||||||
|
|
||||||
## Requirements
|
## Requirements
|
||||||
|
|
||||||
Your datacenter must meet the following requirements prior to configuring the Consul API Gateway:
|
Refer to [Technical Specifications](/docs/api-gateway/tech-specs) for minimum software requirements.
|
||||||
|
|
||||||
- Kubernetes 1.21+
|
|
||||||
- `kubectl` 1.21+
|
|
||||||
- Consul 1.11.2+
|
|
||||||
- HashiCorp Consul Helm chart 0.40.0+
|
|
||||||
|
|
||||||
## Installation
|
## Installation
|
||||||
|
|
||||||
1. Issue the following command to install the Consul API Gateway controller:
|
1. Issue the following command to install the CRDs:
|
||||||
|
|
||||||
<CodeBlockConfig>
|
<CodeBlockConfig>
|
||||||
|
|
||||||
```shell-session
|
```shell-session
|
||||||
$ kubectl apply --kustomize="github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.1.0-beta"
|
$ kubectl apply --kustomize="github.com/hashicorp/consul-api-gateway/config/crd?ref=v0.1.0"
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
||||||
1. Create a `values.yaml` file for your Consul API Gateway deployment. Copy the content below into the `values.yaml` file. The `values.yaml` will be used by the Consul Helm chart. See [Helm Chart Configuration - apigateway](https://www.consul.io/docs/k8s/helm#apigateway) for more available options on how to configure your Consul API Gateway deployment via the Helm chart.
|
1. Create a `values.yaml` file for your Consul API Gateway deployment. Copy the content below into the `values.yaml` file. The `values.yaml` will be used by the Consul Helm chart. See [Helm Chart Configuration - apiGateway](https://www.consul.io/docs/k8s/helm#apigateway) for more available options on how to configure your Consul API Gateway deployment via the Helm chart.
|
||||||
|
|
||||||
<CodeBlockConfig hideClipboard filename="values.yaml">
|
<CodeBlockConfig hideClipboard filename="values.yaml">
|
||||||
|
|
||||||
```yaml
|
```yaml
|
||||||
global:
|
global:
|
||||||
name: consul
|
name: consul
|
||||||
image: 'hashicorp/consul:1.11.2'
|
image: 'hashicorp/consul:1.11.3'
|
||||||
tls:
|
|
||||||
enabled: true
|
|
||||||
connectInject:
|
connectInject:
|
||||||
enabled: true
|
enabled: true
|
||||||
controller:
|
controller:
|
||||||
enabled: true
|
enabled: true
|
||||||
apiGateway:
|
apiGateway:
|
||||||
enabled: true
|
enabled: true
|
||||||
image: hashicorp/consul-api-gateway:0.1.0-beta
|
image: hashicorp/consul-api-gateway:0.1.0
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
@ -64,7 +49,7 @@ Your datacenter must meet the following requirements prior to configuring the Co
|
||||||
<CodeBlockConfig>
|
<CodeBlockConfig>
|
||||||
|
|
||||||
```shell-session
|
```shell-session
|
||||||
$ helm install consul hashicorp/consul --version 0.40.0 --values values.yaml
|
$ helm install consul hashicorp/consul --version 0.41.1 --values values.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
@ -72,14 +57,25 @@ Your datacenter must meet the following requirements prior to configuring the Co
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
1. Verify that the [requirements](#requirements) have been met.
|
1. Verify that the [requirements](#requirements) have been met.
|
||||||
1. Verify that the Consul API Gateway software has been installed and applied (see [Installation](#installation)).
|
1. Verify that the Consul API Gateway CRDs and controller have been installed and applied (see [Installation](#installation)).
|
||||||
1. Configure the artifacts described in [Configuration](#configuration).
|
1. Configure the artifacts described below in [Configuration](#configuration).
|
||||||
|
|
||||||
|
<CodeBlockConfig hideClipboard filename="values.yaml">
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
apiGateway:
|
||||||
|
managedGatewayClass:
|
||||||
|
enabled: true
|
||||||
|
```
|
||||||
|
|
||||||
|
</CodeBlockConfig>
|
||||||
|
|
||||||
1. Issue the `kubectl apply` command to implement the configurations, e.g.:
|
1. Issue the `kubectl apply` command to implement the configurations, e.g.:
|
||||||
|
|
||||||
<CodeBlockConfig>
|
<CodeBlockConfig>
|
||||||
|
|
||||||
```shell-session
|
```shell-session
|
||||||
$ kubectl apply --values gateway-configuration.yaml
|
$ kubectl apply -f gateway.yaml routes.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
@ -142,6 +138,56 @@ Configure the following artifacts to facilitate ingress into your Consul service
|
||||||
- [Gateway](#gateway): Defines the main infrastructure resource that links API gateway components. It specifies the name of the `GatewayClass` and one or more `listeners` (see [Listeners](#listeners)), which specify the logical endpoints bound to the gateway's addresses.
|
- [Gateway](#gateway): Defines the main infrastructure resource that links API gateway components. It specifies the name of the `GatewayClass` and one or more `listeners` (see [Listeners](#listeners)), which specify the logical endpoints bound to the gateway's addresses.
|
||||||
- [Routes](#routes): Specifies the path from the client to the listener.
|
- [Routes](#routes): Specifies the path from the client to the listener.
|
||||||
|
|
||||||
|
-> ** Note:** Add the following `managedGatewayClass` configuration to the `values.yaml` Helm configuration to enable the `GatewayClassConfig` and `GatewayClass` to be created automatically. The gateway, listeners, and routes will need to be configured manually. When `managedGatewayClass` is enabled, the [`serviceType`](/docs/k8s/helm#v-apigateway-managedgatewayclass-servicetype) for a managed `GatewayClass` will also default to `LoadBalancer`, which is appropriate for most deployments to managed Kubernetes cloud offerings (i.e., EKS, GKE, AKS). Other deployments, such as to a [kind](https://kind.sigs.k8s.io/) cluster, may require specifying `NodePort` or `ClusterIP`, instead.
|
||||||
|
|
||||||
|
### GatewayClassConfig
|
||||||
|
|
||||||
|
The `GatewayClassConfig` object describes Consul API Gateway-related configuration parameters for the [`GatewayClass`](#gatewayclass).
|
||||||
|
|
||||||
|
Add the `kind: GatewayClassConfig` option to the gateway values file to declare a gateway class.
|
||||||
|
The following example creates a gateway class configuration called `test-gateway-class-config`:
|
||||||
|
|
||||||
|
<CodeBlockConfig filename="gateway.yaml">
|
||||||
|
|
||||||
|
```yaml
|
||||||
|
apiVersion: api-gateway.consul.hashicorp.com/v1alpha1
|
||||||
|
kind: GatewayClassConfig
|
||||||
|
metadata:
|
||||||
|
name: test-gateway-class-config
|
||||||
|
spec:
|
||||||
|
useHostPorts: true
|
||||||
|
logLevel: 'trace'
|
||||||
|
consul:
|
||||||
|
scheme: 'https'
|
||||||
|
ports:
|
||||||
|
http: 8501
|
||||||
|
grpc: 8502
|
||||||
|
```
|
||||||
|
|
||||||
|
</CodeBlockConfig>
|
||||||
|
|
||||||
|
The following table describes the allowed parameters for the `spec` array:
|
||||||
|
|
||||||
|
| Parameter | Description | Type | Default |
|
||||||
|
| --- | --- | ---- | ------- |
|
||||||
|
| `consul.address` | Specifies the address of the Consul server to communicate with in the gateway pod. If unspecified, the pod will attempt to use a local agent on the host on which the pod is running. | String | N/A |
|
||||||
|
| `consul.authentication.account` | Specifies the Kubernetes service account to use for authentication. | String | N/A |
|
||||||
|
| `consul.authentication.managed` | Set to `true` to enable deployments to run with managed service accounts created by the gateway controller. The `consul.authentication.account` field is ignored when this option is enabled. | Boolean | `false` |
|
||||||
|
| `consul.authentication.method` | Specifies the Consul auth method used for initial authentication by Consul API Gateway. | String | N/A |
|
||||||
|
| `consul.authentication.namespace` | Specifies the Consul namespace to use for authentication. | String | N/A |
|
||||||
|
| `consul.ports.grpc` | Specifies the gRPC port for Consul's xDS server. | Integer | `8502` |
|
||||||
|
| `consul.ports.http` | Specifies the port for Consul's HTTP server. | Integer | `8500` |
|
||||||
|
| `consul.scheme` | Specifies the scheme to use for connecting to Consul. The supported values are `"http"` and `"https"`. | String | `"http"` |
|
||||||
|
| `copyAnnotations.service` | List of annotations to copy to the gateway service. | Array | `["external-dns.alpha.kubernetes.io/hostname"]` |
|
||||||
|
| `image.consulAPIGateway` | The image to use for consul-api-gateway. View available image tags on [DockerHub](https://hub.docker.com/r/hashicorp/consul-api-gateway/tags). | String | `"hashicorp/consul-api-gateway:RELEASE_VERSION"` |
|
||||||
|
| `image.envoy` | Specifies the container image to use for Envoy. View available image tags on [DockerHub](https://hub.docker.com/r/envoyproxy/envoy/tags). | String | `"envoyproxy/envoy:RELEASE_VERSION"` |
|
||||||
|
| `logLevel` | Specifies the error reporting level for logs. You can specify the following values: `error`, `warning`, `info`, `debug`, `trace`. | String | `"info"` |
|
||||||
|
| `nodeSelector` | Specifies a set of parameters that constrain the nodes on which the pod can run. Defining nodes with the `nodeSelector` enables the pod to fit on a node. The selector must match a node's labels for the pod to be scheduled on that node. Refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) for additional information. | Object | N/A |
|
||||||
|
| `serviceType` | Specifies the ingress methods for a service. The following values are supported: <br/>`ClusterIP` <br/>`NodePort` <br/>`LoadBalancer`. | String | N/A |
|
||||||
|
| `useHostPorts` | If set to `true`, then the Envoy container ports are mapped to host ports. | Boolean | `false` |
|
||||||
|
|
||||||
|
Refer to the [Consul API Gateway repository](https://github.com/hashicorp/consul-api-gateway/blob/main/config/crd/bases/api-gateway.consul.hashicorp.com_gatewayclassconfigs.yaml) for the complete specification.
|
||||||
|
|
||||||
### GatewayClass
|
### GatewayClass
|
||||||
|
|
||||||
The `GatewayClass` resource is used as a template for creating `Gateway` resources.
|
The `GatewayClass` resource is used as a template for creating `Gateway` resources.
|
||||||
|
|
@ -172,55 +218,6 @@ spec:
|
||||||
|
|
||||||
Refer to the [Kubernetes Gateway API documentation](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayClass) for details about configuring gateway classes.
|
Refer to the [Kubernetes Gateway API documentation](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayClass) for details about configuring gateway classes.
|
||||||
|
|
||||||
### GatewayClassConfig
|
|
||||||
|
|
||||||
The `GatewayClassConfig` object describes additional Consul API Gateway-related configuration parameters for the `GatewayClass`.
|
|
||||||
|
|
||||||
Add the `kind: GatewayClassConfig` option to the gateway values file to declare a gateway class.
|
|
||||||
The following example creates a gateway class called `test-gateway-class-config`:
|
|
||||||
|
|
||||||
<CodeBlockConfig filename="gateway.yaml">
|
|
||||||
|
|
||||||
```yaml
|
|
||||||
apiVersion: api-gateway.consul.hashicorp.com/v1alpha1
|
|
||||||
kind: GatewayClassConfig
|
|
||||||
metadata:
|
|
||||||
name: test-gateway-class-config
|
|
||||||
spec:
|
|
||||||
useHostPorts: true
|
|
||||||
logLevel: 'trace'
|
|
||||||
consul:
|
|
||||||
scheme: 'https'
|
|
||||||
caSecret: 'consul-ca-cert'
|
|
||||||
ports:
|
|
||||||
http: 8501
|
|
||||||
grpc: 8502
|
|
||||||
```
|
|
||||||
|
|
||||||
</CodeBlockConfig>
|
|
||||||
|
|
||||||
The following table describes the required parameters for the `spec` array:
|
|
||||||
|
|
||||||
| Parameter | Description | Type | Default |
|
|
||||||
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | ------------------------------------------------ |
|
|
||||||
| `consul.address` | Specifies the address of the Consul server to communicate with in the gateway pod. If unspecified, the pod will attempt to use a local agent on the host on which the pod is running. | String | N/A |
|
|
||||||
| `consul.authentication.account` | Specifies the Kubernetes service account to use for authentication. | String | N/A |
|
|
||||||
| `consul.authentication.managed` | Set to `true` to enable deployments to run with managed service accounts created by the gateway controller. The `consul.authentication.account` field is ignored when this option is enabled. | Boolean | `false` |
|
|
||||||
| `consul.authentication.method` | Specifies the Consul auth method used for initial authentication by Consul API Gateway. | String | N/A |
|
|
||||||
| `consul.authentication.namespace` | Specifies the Consul namespace to use for authentication. | String | N/A |
|
|
||||||
| `consul.ports.grpc` | Specifies the gRPC port for Consul's xDS server. | Integer | `8502` |
|
|
||||||
| `consul.ports.http` | Specifies the port for Consul's HTTP server. | Integer | `8500` |
|
|
||||||
| `consul.scheme` | Specifies the scheme to use for connecting to Consul. The supported values are `"http"` and `"https"`. | String | `"http"` |
|
|
||||||
| `copyAnnotations.service` | List of annotations to copy to the gateway service. | Array | `["external-dns.alpha.kubernetes.io/hostname"]` |
|
|
||||||
| `image.consulAPIGateway` | The image to use for consul-api-gateway. | String | `"hashicorp/consul-api-gateway:RELEASE_VERSION"` |
|
|
||||||
| `image.envoy` | Specifies the container image to use for Envoy. | String | `"envoyproxy/envoy:v1.19-latest"` |
|
|
||||||
| `logLevel` | Specifies the error reporting level for logs. You can specify the following values: `fatal`, `error`, `warning`, `info`, `debug`, `trace`. | String | `"info"` |
|
|
||||||
| `nodeSelector` | Specifies a set of parameters that constrain the nodes on which the pod can run. Defining nodes with the `nodeSelector` enables the pod to fit on a node. The selector must match a node's labels for the pod to be scheduled on that node. Refer to the [Kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/) for additional information. | Object | N/A |
|
|
||||||
| `serviceType` | Specifies the ingress methods for a service. The following values are supported: <br/>`ClusterIP` <br/>`NodePort` <br/>`LoadBalancer`. | String | N/A |
|
|
||||||
| `useHostPorts` | If set to `true`, then the Envoy container ports are mapped to host ports. | Boolean | `false` |
|
|
||||||
|
|
||||||
Refer to the [Consul API Gateway repository](https://github.com/hashicorp/consul-api-gateway/blob/main/config/crd/bases/api-gateway.consul.hashicorp.com_gatewayclassconfigs.yaml) for the complete specification.
|
|
||||||
|
|
||||||
### Gateway
|
### Gateway
|
||||||
|
|
||||||
The gateway configuration is the main infrastructure resource that links API gateway components. It specifies the name of the `GatewayClass` and one or more `listeners`.
|
The gateway configuration is the main infrastructure resource that links API gateway components. It specifies the name of the `GatewayClass` and one or more `listeners`.
|
||||||
|
|
@ -307,3 +304,14 @@ spec:
|
||||||
```
|
```
|
||||||
|
|
||||||
</CodeBlockConfig>
|
</CodeBlockConfig>
|
||||||
|
|
||||||
|
|
||||||
|
### MeshService
|
||||||
|
|
||||||
|
The `MeshService` configuration holds a reference to an externally-managed Consul service mesh service and can be used as a `backendRef` for a [`Route`](#route).
|
||||||
|
|
||||||
|
| Parameter | Description | Type | Default |
|
||||||
|
| ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- | --------------- |
|
||||||
|
| `name` | Specifies the service name for a Consul service. It is assumed this service will exist in either the `consulDestinationNamespace` or mirrored Consul namespace from where this custom resource is defined, depending on the Helm configuration.
|
||||||
|
|
||||||
|
Refer to the [Consul API Gateway repository](https://github.com/hashicorp/consul-api-gateway/blob/main/config/crd/bases/api-gateway.consul.hashicorp.com_meshservices.yaml) for the complete specification.
|
||||||
|
|
@ -0,0 +1,45 @@
|
||||||
|
---
|
||||||
|
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 can be deployed on Kubernetes-based runtime environments and requires that Consul service mesh be deployed on the Kubernetes cluster.
|
||||||
|
|
||||||
|
API Gateway routes traffic to services connected to the same service mesh. Those services can be running on the same Kubernetes cluster as the API Gateway, a different Kubernetes cluster, or another runtime, as long as they are connected to the same service mesh deployment and reachable over the network.
|
||||||
|
|
||||||
|
Consul API Gateway implements, and is configured through, 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.
|
||||||
|
|
||||||
|
### Supported Kubernetes Gateway Specification Features
|
||||||
|
|
||||||
|
The Consul API Gateway supports a subset of the Kubernetes [v1alpha2 Gateway API specification](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/). The following table
|
||||||
|
describes the supported features of the specification. For a complete list of features, including the list of gateway and route statuses and an explanation on how they
|
||||||
|
are used, see the [documentation in our GitHub repo](https://github.com/hashicorp/consul-api-gateway/blob/main/dev/docs/supported-features.md).
|
||||||
|
|
||||||
|
| Kubernetes Object | Description |
|
||||||
|
| ----- | ----------------------------- |
|
||||||
|
| [`GatewayClass`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.GatewayClass) | <ul><li>Parameter specification via `GatewayClassConfig` CRD</li><li>Controller matching on `"hashicorp.com/consul-api-gateway-controller"`</li></ul> |
|
||||||
|
| [`Gateway`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.Gateway) | <ul><li>Supported protocols: `HTTP`, `HTTPS`, `TCP`</li><li>Header-based hostname matching (no SNI support)</li><li>Supported filters: header addition, removal, and setting</li><li>TLS modes supported: `terminate`</li><li>Certificate types supported: `core/v1/Secret`</li><li>Extended options: TLS version and cipher constraints</li></ul> |
|
||||||
|
| [`HTTPRoute`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.HTTPRoute) | <ul><li>Weight-based load balancing</li><li>Supported rules: path, header, query, and method-based matching</li><li>Supported filters: header addition, removal, and setting</li><li>Supported backend types: <ol><li>`core/v1/Service` (must map to a registered Consul service)</li><li>`api-gateway.consul.hashicorp.com/v1alpha1/MeshService`</li></ol></li></ul> |
|
||||||
|
| [`TCPRoute`](https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/#gateway.networking.k8s.io/v1alpha2.TCPRoute) | <ul><li>Supported backend types: <ol><li>`core/v1/Service` (must map to a registered Consul service)</li><li>`api-gateway.consul.hashicorp.com/v1alpha1/MeshService`</li></ol></li></ul> |
|
||||||
|
|
||||||
|
## 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).
|
||||||
|
|
||||||
|
|
@ -0,0 +1,69 @@
|
||||||
|
---
|
||||||
|
layout: docs
|
||||||
|
page_title: Consul API Gateway Technical Specifications
|
||||||
|
description: >-
|
||||||
|
This topic describes technical specifications for Consul API Gateway.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Technical Specifications
|
||||||
|
|
||||||
|
This topic describes the technical specifications associated with using Consul API Gateway.
|
||||||
|
|
||||||
|
## Requirements
|
||||||
|
|
||||||
|
Verify that your environment meets the following requirements prior to using Consul API Gateway.
|
||||||
|
|
||||||
|
### Datacenter Requirements
|
||||||
|
|
||||||
|
Your datacenter must meet the following requirements prior to configuring the Consul API Gateway:
|
||||||
|
|
||||||
|
- Kubernetes 1.21+
|
||||||
|
- `kubectl` 1.21+
|
||||||
|
- Consul 1.11.2+
|
||||||
|
- HashiCorp Consul Helm chart 0.41.1+
|
||||||
|
- Consul Service Mesh must be deployed on the Kubernetes cluster that API Gateway is deployed on.
|
||||||
|
|
||||||
|
### TCP Port Requirements
|
||||||
|
|
||||||
|
The following table describes the TCP port requirements for each component of the API Gateway.
|
||||||
|
|
||||||
|
| Port | Description | Component |
|
||||||
|
| ---- | ----------- | --------- |
|
||||||
|
| 9090 | Secret discovery service (SDS) | Gateway controller pod <br/> Gateway instance pod |
|
||||||
|
| 20000 | Kubernetes readiness probe | Gateway instance pod |
|
||||||
|
| Configurable | Port for scraping Prometheus metrics. Disabled by default. | Gateway controller pod |
|
||||||
|
|
||||||
|
## Consul Server Deployments
|
||||||
|
|
||||||
|
- Consul Editions supported: OSS and Enterprise
|
||||||
|
- Supported Consul Server deployment types:
|
||||||
|
- Self-Managed
|
||||||
|
- HCP Consul
|
||||||
|
|
||||||
|
## Deployment Environments
|
||||||
|
|
||||||
|
Consul API Gateway can be deployed in the following Kubernetes-based environments:
|
||||||
|
|
||||||
|
- Generic Kubernetes
|
||||||
|
- AWS Elastic Kubernetes Service (EKS)
|
||||||
|
- Google Kubernetes Engine (GKE)
|
||||||
|
- Azure Kubernetes Service (AKS)
|
||||||
|
|
||||||
|
## Kubernetes Gateway API Specification
|
||||||
|
|
||||||
|
Supported version of the Gateway API spec: v1alpha2
|
||||||
|
|
||||||
|
|
||||||
|
## Resource Allocations
|
||||||
|
|
||||||
|
The following resources are allocated for each component of the API Gateway.
|
||||||
|
|
||||||
|
### Gateway Controller Pod
|
||||||
|
|
||||||
|
* **CPU**: None. Either the namespace or cluster default is allocated, depending on the Kubernetes cluster configuration.
|
||||||
|
* **Memory**: None. Either the the namespace or cluster default is allocated, depending on the Kubernetes cluster configuration.
|
||||||
|
|
||||||
|
### Gateway Instance Pod
|
||||||
|
|
||||||
|
* **CPU**: None. Either the namespace or cluster default is allocated, depending on the Kubernetes cluster configuration.
|
||||||
|
* **Memory**: None. Either the namespace or cluster default is allocated, depending on the Kubernetes cluster configuration.
|
||||||
|
|
@ -375,9 +375,22 @@
|
||||||
]
|
]
|
||||||
},
|
},
|
||||||
{
|
{
|
||||||
"title": "Consul API Gateway <sup>BETA</sup>",
|
"title": "Consul API Gateway",
|
||||||
|
"routes": [
|
||||||
|
{
|
||||||
|
"title": "Overview",
|
||||||
"path": "api-gateway"
|
"path": "api-gateway"
|
||||||
},
|
},
|
||||||
|
{
|
||||||
|
"title": "Usage",
|
||||||
|
"path": "api-gateway/api-gateway-usage"
|
||||||
|
},
|
||||||
|
{
|
||||||
|
"title": "Technical Specifications",
|
||||||
|
"path": "api-gateway/tech-specs"
|
||||||
|
}
|
||||||
|
]
|
||||||
|
},
|
||||||
{
|
{
|
||||||
"title": "Kubernetes",
|
"title": "Kubernetes",
|
||||||
"routes": [
|
"routes": [
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue