From 86754cfe5a51adce737d51a264474d0bf3051ec2 Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 12:55:15 -0700 Subject: [PATCH] Update website/content/docs/api-gateway/tech-specs.mdx Co-authored-by: Nathan Coleman --- 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 f74b42b38b..213b43550a 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 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