mirror of https://github.com/status-im/consul.git
Update website/content/docs/api-gateway/tech-specs.mdx
This commit is contained in:
parent
86754cfe5a
commit
f0e8d44c80
|
@ -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. |
|
| 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. |
|
| Datacenter Federation | When multiple Consul datacenters are federated together, API Gateway can only be deployed in the primary datacenter. |
|
||||||
| 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. |
|
| Routing between Datacenters | When multiple Consul datacenters are federated 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
|
## Deployment Environments
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue