Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: Update terminating-gateway-config-entry #9770

Merged
merged 1 commit into from
Mar 11, 2021
Merged

Docs: Update terminating-gateway-config-entry #9770

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions website/content/docs/connect/config-entries/terminating-gateway.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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',
Expand Down