status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #14534 from hashicorp/docs/capigw-tech-spec-update 

Docs: add limitations to Tech Specs
This commit is contained in:
Jeff Apple 2022-09-08 14:47:39 -07:00 committed by GitHub
parent 9ff0be6950 776c98d109
commit deda99a387
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/content/docs/api-gateway/tech-specs.mdx
View File

@ -42,6 +42,16 @@ The following table describes the TCP port requirements for each component of th
- Self-Managed - Self-Managed
- HCP Consul - HCP Consul
### Limited Support of some Consul Features
The following table lists API Gateway limitations related to specific Consul features
| Consul Feature | Limitation |
| -------------- | ---------- |
| [Admin partitions](/docs/enterprise/admin-partitions) | You can only deploy Consul API Gateway into the `default` admin partition. |
| Datacenter federation | If you are connecting multiple Consul datacenters to create a federated network, you can only deploy Consul API Gateway in the `primary` datacenter. |
| Routing between datacenters | If you are connecting multiple Consul datacenters to create a federated network, API Gateway can only route traffic to Services in the local datacenter. However, API Gateway can route to Services in other Kubernetes clusters when they are in the same Consul datacenter. Refer to [Single Consul Datacenter in Multiple Kubernetes Clusters](/docs/k8s/deployment-configurations/single-dc-multi-k8s) for more details. |
## Deployment Environments ## Deployment Environments
Consul API Gateway can be deployed in the following Kubernetes-based environments: Consul API Gateway can be deployed in the following Kubernetes-based environments: