github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Browse Source

Update website/content/docs/api-gateway/tech-specs.mdx 

Co-authored-by: Nathan Coleman <nathan.coleman@hashicorp.com>
pull/14534/head
Jeff Apple 2 years ago committed by GitHub
parent
a1eb38213a
commit
402ddd6dcd
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Split View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      website/content/docs/api-gateway/tech-specs.mdx

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

@ -49,7 +49,7 @@ The following table lists API Gateway limitations related to specific Consul fea
| Consul Feature | Limitation |
| -------------- | ---------- |
| Admin Partitions | API Gateway can deployed only in the default Admin Partition. |
| Data Center Federation | When multiple Consul Data Centers are fererated together, API gateway can only be deployed in the Priary Data Center. |
| 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. |
## Deployment Environments

Write Preview
Loading…
Cancel
Save