From af2086fbeb90a4b34809c6fab220e432d0bd3bab Mon Sep 17 00:00:00 2001 From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Date: Fri, 10 Nov 2023 14:05:35 -0800 Subject: [PATCH] docs: Fix nav link for L7 traffic (#19606) * fix * Sameness merge error --- .../content/docs/connect/manage-traffic/failover/sameness.mdx | 4 +--- website/data/docs-nav-data.json | 2 +- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/website/content/docs/connect/manage-traffic/failover/sameness.mdx b/website/content/docs/connect/manage-traffic/failover/sameness.mdx index 98117bd283..2fb56b72d1 100644 --- a/website/content/docs/connect/manage-traffic/failover/sameness.mdx +++ b/website/content/docs/connect/manage-traffic/failover/sameness.mdx @@ -88,14 +88,12 @@ spec: -When a sameness group is configured as the failover default, sameness group fail over takes place when a service resolver configuration entry does not implement more specific failover behavior. When a service resolver is defined for an upstream, it is used instead of the sameness group for default failover behavior. +When a sameness group is configured as the failover default, sameness group failover takes place when a service resolver configuration entry does not implement more specific failover behavior. When a service resolver is defined for an upstream, it is used instead of the sameness group for default failover behavior. All services registered in the admin partition must failover to another member of the sameness group. You cannot choose subsets of services to use the sameness group as the failover default. If groups do not have identical services, or if a service is registered to some group members but not all members, this failover strategy may produce errors. For more information about specifying sameness group members and failover, refer to [sameness group configuration entry reference](/consul/docs/connects/config-entries/sameness-group). -All services registered in the admin partition must fail over to another member of the sameness group. You cannot choose subsets of services to use the sameness group as the failover default. If groups do not have identical services, or if a service is registered to some group members but not all members, this failover strategy may produce errors. - ### Failover with a service resolver configuration entry When the sameness group is not configured as the failover default, you can reference the sameness group in a service resolver configuration entry. This approach enables you to use the sameness group as the failover destination for some services registered to group members. diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json index 6864013e8d..84c08a5c39 100644 --- a/website/data/docs-nav-data.json +++ b/website/data/docs-nav-data.json @@ -1586,7 +1586,7 @@ "routes": [ { "title": "Overview", - "href": "/docs/connect/l7-traffic" + "href": "/docs/connect/manage-traffic" }, { "title": "Configure failover services",