From 193eeaee7a9526b09802c63d53d39975ef65a8a8 Mon Sep 17 00:00:00 2001 From: Nathan Coleman Date: Thu, 8 Sep 2022 15:56:28 -0400 Subject: [PATCH] Update website/content/docs/api-gateway/tech-specs.mdx --- website/content/docs/api-gateway/tech-specs.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/api-gateway/tech-specs.mdx b/website/content/docs/api-gateway/tech-specs.mdx index 213b43550..bda188ca8 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -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