From ec508e492e14da93a0b4752e6509791d47937a58 Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 11:38:27 -0700 Subject: [PATCH 1/6] Docs: add limitations to Tech Specs --- website/content/docs/api-gateway/tech-specs.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/website/content/docs/api-gateway/tech-specs.mdx b/website/content/docs/api-gateway/tech-specs.mdx index e49934919..c3de21f2d 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -42,6 +42,16 @@ The following table describes the TCP port requirements for each component of th - Self-Managed - HCP Consul +### Limited Support of some Consul Features + +The following table lists API Gateway limitations relted to specific Consul features + +| 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. | +| 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 Consul API Gateway can be deployed in the following Kubernetes-based environments: From ce4ec3e6b8de07a2bd7716e5c078cab06229efaa Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 12:51:44 -0700 Subject: [PATCH 2/6] 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 c3de21f2d..f62458eb8 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -44,7 +44,7 @@ The following table describes the TCP port requirements for each component of th ### Limited Support of some Consul Features -The following table lists API Gateway limitations relted to specific Consul features +The following table lists API Gateway limitations related to specific Consul features | Consul Feature | Limitation | | -------------- | ---------- | From 0648e83bca4e7d6f0af97b4fceff5d99b127c9cc Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 12:54:02 -0700 Subject: [PATCH 3/6] 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 f62458eb8..f74b42b38 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -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 From c9251d2aaa1838b44a2edea7e3a95f1821880aca 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 4/6] 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 f74b42b38..213b43550 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 From 193eeaee7a9526b09802c63d53d39975ef65a8a8 Mon Sep 17 00:00:00 2001 From: Nathan Coleman Date: Thu, 8 Sep 2022 15:56:28 -0400 Subject: [PATCH 5/6] 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 From c12c0a83762131f93a6749f93ce0db302343167b Mon Sep 17 00:00:00 2001 From: Jeff Apple <79924108+Jeff-Apple@users.noreply.github.com> Date: Thu, 8 Sep 2022 14:41:06 -0700 Subject: [PATCH 6/6] Update website/content/docs/api-gateway/tech-specs.mdx --- website/content/docs/api-gateway/tech-specs.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/content/docs/api-gateway/tech-specs.mdx b/website/content/docs/api-gateway/tech-specs.mdx index bda188ca8..7471d2fd8 100644 --- a/website/content/docs/api-gateway/tech-specs.mdx +++ b/website/content/docs/api-gateway/tech-specs.mdx @@ -48,9 +48,9 @@ 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. | -| 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 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. | +| [Admin partitions](/docs/enterprise/admin-partitions) | You can only deploy Consul API Gateway into the `default` admin partition. | +| 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. | ## Deployment Environments