luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

Docs: add limitations to Tech Specs

This commit is contained in:
Jeff Apple 2022-09-08 11:38:27 -07:00 committed by GitHub
parent 331c756471
commit ec508e492e
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
- HCP Consul
### Limited Support of some Consul Features
The following table lists API Gateway limitations relted to specific Consul features
| Consul Feature | Limitation |
| -------------- | ---------- |
| Admin Partitions | API Gateway can deployed only in the default Admin Partition. |
| Data Center Federation | When multiple Consul Data Centers are fererated together, API gateway can only be deployed in the Priary Data Center. |
| Routing between Data Centers | When multiple Consul Data Centers are fererated together, API gateway can route traffic only to Services in the local Data Center. Howeve, API Gateway can route to Services in othe Kubernetes clusters when they are in the same Consul Data Center. See [Single Consul Datacenter in Multiple Kubernetes Clusters](https://www.consul.io/docs/k8s/deployment-configurations/single-dc-multi-k8s) for more details. |
## Deployment Environments
Consul API Gateway can be deployed in the following Kubernetes-based environments: