Skip to content

Commit

Permalink
Update website/content/docs/api-gateway/tech-specs.mdx
Browse files Browse the repository at this point in the history
  • Loading branch information
@nathancoleman
nathancoleman authored Sep 8, 2022
1 parent 86754cf commit f0e8d44
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion website/content/docs/api-gateway/tech-specs.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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 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

Expand Down

0 comments on commit f0e8d44

Please sign in to comment.