status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-26 21:51:39 +00:00
Code Issues Projects Releases Wiki Activity

Update tech-specs.mdx (#14840)

Browse Source
This commit is contained in:
Luke Kysow 2022-10-03 09:21:42 -07:00 committed by GitHub
parent ad7295e5d9
commit de04344e47
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/api-gateway/tech-specs.mdx
View File

@ -48,7 +48,7 @@ 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. |
| [Admin partitions](/docs/enterprise/admin-partitions) | You can only deploy Consul API Gateway into the `default` admin partition and it can only route to other services within that partition, i.e. you cannot route to services in other admin partitions. |
| 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, API Gateway can only route traffic 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. Refer to [Single Consul Datacenter in Multiple Kubernetes Clusters](/docs/k8s/deployment-configurations/single-dc-multi-k8s) for more details. |