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

Update website/content/docs/api-gateway/tech-specs.mdx 

Co-authored-by: Nathan Coleman <nathan.coleman@hashicorp.com>
This commit is contained in:
Jeff Apple 2022-09-08 12:55:15 -07:00 committed by GitHub
parent 402ddd6dcd
commit 86754cfe5a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -50,7 +50,7 @@ The following table lists API Gateway limitations related to specific Consul fea
| -------------- | ---------- |
| Admin Partitions | API Gateway can deployed only in the default Admin Partition. |
| Datacenter Federation | When multiple Consul datacenters are federated together, API Gateway can only be deployed in the primary datacenter. |
| 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. |
| Routing between Datacenters | When multiple Consul datacenters are fe=derated together, API gateway can route traffic only 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. 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