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

Merge pull request #9770 from hashicorp/docs/fix-terminating-gateway-config-entry 

Docs: Update terminating-gateway-config-entry
This commit is contained in:
Freddy 2021-03-11 12:42:20 -07:00 committed by GitHub
parent 7053fcdd0c f4fe262a79
commit 43eeb66439
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -9,7 +9,7 @@ description: >-
# Terminating Gateway
-> **v1.8.4+:** On Kubernetes, the `ServiceSplitter` custom resource is supported in Consul versions 1.8.4+.<br />
-> **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
@ -651,10 +651,11 @@ and configure default certificates for mutual TLS. Also override the SNI and CA
{
name: 'Services',
type: 'array<LinkedService>: <optional>',
description: `A list of services to link
description: 'A list of services to link
with the gateway. The gateway will proxy traffic to these services. These linked services
must be registered with Consul for the gateway to discover their addresses. They must also
be registered in the same Consul datacenter as the terminating gateway.`,
be registered in the same Consul datacenter as the terminating gateway. If Consul ACLs are
enabled, the Terminatig Gateway's ACL token must grant `service:write` for all linked services.',
children: [
{
name: 'Name',