Remove datacenter federation from limited support matrix

hashicorp · Nov 7, 2022 · 5728d69 · 5728d69
1 parent a2a2d60
commit 5728d69
Showing 1 changed file with 0 additions and 1 deletion.
diff --git a/website/content/docs/api-gateway/tech-specs.mdx b/website/content/docs/api-gateway/tech-specs.mdx
@@ -49,7 +49,6 @@ The following table lists API Gateway limitations related to specific Consul fea
 | Consul Feature | Limitation |
 | -------------- | ---------- |
 | [Admin partitions](/docs/enterprise/admin-partitions) | You can only deploy Consul API Gateway into the `default` admin partition. You can route to services in other admin partitions through peered connections. Refer to [Route Traffic to Peered Services](/consul/docs/api-gateway/usage/route-to-peered-services) for additional information. |
-| Datacenter federation | If you are connecting multiple Consul datacenters to create a federated network, you can only deploy Consul API Gateway in the `primary` datacenter. |
 | Routing between datacenters | If you are connecting multiple Consul datacenters to create a federated network, you can route to services in other datacenters through peered connections. Refer to [Route Traffic to Peered Services](/consul/docs/api-gateway/usage/route-to-peered-services) for additional information. |
 
 ## Deployment Environments