luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

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 <dyu@hashicorp.com>
This commit is contained in:
hc-github-team-consul-core 2023-06-13 19:08:57 -04:00 committed by GitHub
parent be015331a8
commit dc9f45e1d7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 0 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/connect/config-entries/exported-services.mdx
View File

@ -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.

2
website/content/docs/connect/config-entries/mesh.mdx
View File

@ -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.

3
website/content/docs/connect/config-entries/terminating-gateway.mdx
View File

@ -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+.<br />
**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