From f233aef14d51cae285373715d36ce5d6b647e625 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Tue, 13 Jun 2023 19:08:57 -0400 Subject: [PATCH] Backport of Remove extraneous version info for Config entries into release/1.16.x (#17718) * backport of commit c02c4445ccf3cd3dd15199932d81de78b32c1210 * backport of commit 3237e24a11496172837fb05a0dcdbd0266e8710e * backport of commit 3bbd88fb79094dc641cd1ff43e8a8cdde92df3d9 --------- Co-authored-by: David Yu --- .../content/docs/connect/config-entries/exported-services.mdx | 2 -- website/content/docs/connect/config-entries/mesh.mdx | 2 -- .../docs/connect/config-entries/terminating-gateway.mdx | 3 --- 3 files changed, 7 deletions(-) diff --git a/website/content/docs/connect/config-entries/exported-services.mdx b/website/content/docs/connect/config-entries/exported-services.mdx index 089eeb572314..c7811d8d9b48 100644 --- a/website/content/docs/connect/config-entries/exported-services.mdx +++ b/website/content/docs/connect/config-entries/exported-services.mdx @@ -9,8 +9,6 @@ description: >- This topic describes the `exported-services` configuration entry type. The `exported-services` configuration entry enables Consul to export service instances to other clusters from a single file and connect services across clusters. For additional information, refer to [Cluster Peering](/consul/docs/connect/cluster-peering) and [Admin Partitions](/consul/docs/enterprise/admin-partitions). --> **v1.11.0+:** This config entry is supported in Consul versions 1.11.0+. - ## Introduction To configure Consul to export services contained in a Consul Enterprise admin partition or Consul OSS datacenter to one or more additional clusters, create a new configuration entry and declare `exported-services` in the `kind` field. This configuration entry enables you to route traffic between services in different clusters. diff --git a/website/content/docs/connect/config-entries/mesh.mdx b/website/content/docs/connect/config-entries/mesh.mdx index a323a6d90f17..98760c068c04 100644 --- a/website/content/docs/connect/config-entries/mesh.mdx +++ b/website/content/docs/connect/config-entries/mesh.mdx @@ -7,8 +7,6 @@ description: >- # Mesh Configuration Entry --> **v1.10.0+:** This configuration entry is supported in Consul versions 1.10.0+. - The `mesh` configuration entry allows you to define a global default configuration that applies to all service mesh proxies. Settings in this config entry apply across all namespaces and federated datacenters. diff --git a/website/content/docs/connect/config-entries/terminating-gateway.mdx b/website/content/docs/connect/config-entries/terminating-gateway.mdx index e0c1ff6032cf..9c0804f9c39d 100644 --- a/website/content/docs/connect/config-entries/terminating-gateway.mdx +++ b/website/content/docs/connect/config-entries/terminating-gateway.mdx @@ -7,9 +7,6 @@ description: >- # Terminating Gateway Configuration Entry --> **v1.8.4+:** On Kubernetes, the `TerminatingGateway` custom resource is supported in Consul versions 1.8.4+.
-**v1.8.0+:** On other platforms, this config entry is supported in Consul versions 1.8.0+. - The `terminating-gateway` config entry kind (`TerminatingGateway` on Kubernetes) allows you to configure terminating gateways to proxy traffic from services in the Consul service mesh to services registered with Consul that do not have a [service mesh sidecar proxy](/consul/docs/connect/proxies). The configuration is associated with the name of a gateway service