hashicorp · eddie-rowe · Mar 24, 2023 · Mar 15, 2023 · Mar 15, 2023 · Mar 21, 2023
@@ -157,7 +157,7 @@ information.
 - `-segment` ((#\_segment)) <EnterpriseAlert inline /> - This flag is used to set
   the name of the network segment the agent belongs to. An agent can only join and
   communicate with other agents within its network segment. Ensure the [join
-  operation uses the correct port for this segment](/consul/docs/enterprise/network-segments#join_a_client_to_a_segment).
+  operation uses the correct port for this segment](/consul/docs/enterprise/network-segments/create-network-segment#configure-clients-to-join-segments).
   Review the [Network Segments documentation](/consul/docs/enterprise/network-segments/create-network-segment)
   for more details. By default, this is an empty string, which is the `<default>`
   network segment.
@@ -490,7 +490,7 @@ information.
   the data directory. This is useful when running multiple Consul agents on the same
   host for testing. This defaults to false in Consul prior to version 0.8.5 and in
   0.8.5 and later defaults to true, so you must opt-in for host-based IDs. Host-based
-  IDs are generated using [gopsutil](https://github.com/shirou/gopsutil/tree/master/v3/host), which
+  IDs are generated using [gopsutil](https://github.com/shirou/gopsutil/), which
   is shared with HashiCorp's [Nomad](https://www.nomadproject.io/), so if you opt-in
   to host-based IDs then Consul and Nomad will use information on the host to automatically
   assign the same ID in both systems.

@@ -924,7 +924,7 @@ Refer to the [formatting specification](https://golang.org/pkg/time/#ParseDurati
       [`acl.tokens.agent_recovery`](#acl_tokens_agent_recovery).**
 
     - `config_file_service_registration` ((#acl_tokens_config_file_service_registration)) - Specifies the ACL
-      token the agent uses to register services and checks from [service](/consul/docs/services/usage/define-services) and [check](/consul/docs/usage/checks) definitions 
+      token the agent uses to register services and checks from [service](/consul/docs/services/usage/define-services) and [check](/consul/docs/services/usage/checks) definitions 
       specified in configuration files or fragments passed to the agent using the `-hcl`
       flag.
 

@@ -62,7 +62,7 @@ its consequences during outage situations). Reaping is similar to leaving,
 causing all associated services to be deregistered.
 
 ## Limit traffic rates
-You can define a set of rate limiting configurations that help operators protect Consul servers from excessive or peak usage. The configurations enable you to gracefully degrade Consul servers to avoid a global interruption of service. Consul supports global server rate limiting, which lets configure Consul servers to deny requests that exceed the read or write limits. Refer to [Traffic Rate Limits Overview](/consul/docs/agent/limits/limit-traffic-rates).
+You can define a set of rate limiting configurations that help operators protect Consul servers from excessive or peak usage. The configurations enable you to gracefully degrade Consul servers to avoid a global interruption of service. Consul supports global server rate limiting, which lets configure Consul servers to deny requests that exceed the read or write limits. Refer to [Traffic Rate Limits Overview](/consul/docs/agent/limits).
 
 ## Requirements
 

@@ -23,7 +23,7 @@ The overall process for enabling the WAL LogStore backend for one server consist
 
 ## Requirements
 
-- Consul v1.15 or later is required for all servers in the datacenter. Refer to the [standard upgrade procedure](/consul/docs/upgrading/general-process) and the [1.15 upgrade notes](/consul/docs/upgrading/upgrade-specific#consul-1-15-x) for additional information.
+- Consul v1.15 or later is required for all servers in the datacenter. Refer to the [standard upgrade procedure](/consul/docs/upgrading/instructions/general-process) and the [1.15 upgrade notes](/consul/docs/upgrading/upgrade-specific#consul-1-15-x) for additional information.
 - A Consul cluster with at least three nodes are required to safely test the WAL backend without downtime.
 
 We recommend taking the following additional measures:

@@ -7,7 +7,7 @@ description: >-
 
 # Monitor Raft metrics and logs for WAL
 
-This topic describes how to monitor Raft metrics and logs if you are testing the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly. Refer to [Enable the experimental WAL LogStore backend](/consul/docs/agent/wal-logstore/index) for additional information about the WAL backend.
+This topic describes how to monitor Raft metrics and logs if you are testing the WAL backend. We strongly recommend monitoring the Consul cluster, especially the target server, for evidence that the WAL backend is not functioning correctly. Refer to [Enable the experimental WAL LogStore backend](/consul/docs/agent/wal-logstore/enable) for additional information about the WAL backend.
 
 !> **Upgrade warning:** The WAL LogStore backend is experimental.
 

@@ -168,7 +168,7 @@ The following example creates a route named `example-route` in namespace `gatewa
 
 ### rules.filters
 
-The `filters` block defines steps for processing requests. You can configure filters to modify the properties of matching incoming requests and enable Consul API Gateway features, such as rewriting path prefixes (refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage#reroute-http-requests) for additional information).
+The `filters` block defines steps for processing requests. You can configure filters to modify the properties of matching incoming requests and enable Consul API Gateway features, such as rewriting path prefixes (refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage/reroute-http-requests) for additional information).
 
 * Type: Array of objects
 * Required: Optional
@@ -203,7 +203,7 @@ Specifies rules for rewriting the URL of incoming requests when `rules.filters.t
 
 ### rules.filters.urlRewrite.path
 
-Specifies a list of objects that determine how Consul API Gateway rewrites URL paths (refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage#reroute-http-requests) for additional information).
+Specifies a list of objects that determine how Consul API Gateway rewrites URL paths (refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage/reroute-http-requests) for additional information).
 
 The following table describes the parameters for `path`:
 

@@ -18,7 +18,7 @@ This topic describes how to configure Consul API Gateway to route traffic to ser
 
 ## Configuration
 
-Specify the following fields in your `MeshService` configuration to use this feature. Refer to the [MeshService configuration reference](/consul/docs/api-gateway/configuration/mesh) for details about the parameters.
+Specify the following fields in your `MeshService` configuration to use this feature. Refer to the [MeshService configuration reference](/consul/docs/api-gateway/configuration/meshservice) for details about the parameters.
 
 - [`name`](/consul/docs/api-gateway/configuration/meshservice#name)
 - [`peer`](/consul/docs/api-gateway/configuration/meshservice#peer)

@@ -51,7 +51,7 @@ To mitigate these risks, we recommend a maximum of 5,000 Consul client agents in
 
 1. Run exactly one Consul agent per host in the infrastructure.
 1. Break up the single Consul datacenter into multiple smaller datacenters.
-1. Enterprise users can define [network segments](/consul/docs/enterprise/network-segments) to divide the single gossip pool in the Consul datacenter into multiple smaller pools.
+1. Enterprise users can define [network segments](/consul/docs/enterprise/network-segments/network-segments-overview) to divide the single gossip pool in the Consul datacenter into multiple smaller pools.
 
 If appropriate for your use case, we recommend breaking up a single Consul datacenter into multiple smaller datacenters. Running multiple datacenters reduces your network’s blast radius more than applying network segments.
 

@@ -19,10 +19,13 @@ To use cluster peering features, make sure your Consul environment meets the fol
 
 In addition, the following service mesh components are required in order to establish cluster peering connections:
 
-- [Mesh gateways](#mesh-gateway-requirements)
-- [Sidecar proxies](#sidecar-proxy-requirements)
-- [Exported services](#exported-service-requirements)
-- [ACLs](#acl-requirements)
+- [Cluster peering technical specifications](#cluster-peering-technical-specifications)
+  - [Requirements](#requirements)
+    - [Mesh gateway requirements](#mesh-gateway-requirements)
+      - [Mesh gateway modes](#mesh-gateway-modes)
+  - [Sidecar proxy requirements](#sidecar-proxy-requirements)
+  - [Exported service requirements](#exported-service-requirements)
+  - [ACL requirements](#acl-requirements)
 
 ### Mesh gateway requirements
 
@@ -45,7 +48,7 @@ Refer to [mesh gateway modes](/consul/docs/connect/gateways/mesh-gateway#modes)
 
 ## Sidecar proxy requirements
 
-The Envoy proxies that function as sidecars in your service mesh require configuration in order to properly route traffic to peers. Sidecar proxies are defined in the [service definition](/consul/docs/services/usage/defin-services).
+The Envoy proxies that function as sidecars in your service mesh require configuration in order to properly route traffic to peers. Sidecar proxies are defined in the [service definition](/consul/docs/services/usage/define-services).
 
 - Configure the `proxy.upstreams` parameters to route traffic to the correct service, namespace, and peer. Refer to the [`upstreams`](/consul/docs/connect/registration/service-registration#upstream-configuration-reference) documentation for details.
 - The `proxy.upstreams.destination_name` parameter is always required.
@@ -56,7 +59,7 @@ The Envoy proxies that function as sidecars in your service mesh require configu
 
 The `exported-services` configuration entry is required in order for services to communicate across partitions with cluster peering connections.
 
-Basic guidance on using the `exported-services` configuration entry is included in [Establish cluster peering connections](/consul/docs/connect/cluster-peering/usage/create-cluster-peering).
+Basic guidance on using the `exported-services` configuration entry is included in [Establish cluster peering connections](/consul/docs/k8s/connect/cluster-peering/usage/establish-peering).
 
 Refer to the [`exported-services` configuration entry](/consul/docs/connect/config-entries/exported-services) reference for more information.
 

@@ -125,7 +125,7 @@ For more information, including optional flags and parameters, refer to the [`co
   $ curl --request DELETE --header "X-Consul-Token: b23b3cad-5ea1-4413-919e-c76884b9ad60" http://127.0.0.1:8500/v1/peering/cluster-02
   ```
 
-This endpoint does not return a response. For more information, including optional parameters, refer to the [`/peering` endpoint reference](/consul/api-docs/peering/consul/api-docs/peering#delete-a-peering-connection).
+This endpoint does not return a response. For more information, including optional parameters, refer to the [`/peering` endpoint reference](/consul/api-docs/peering#delete-a-peering-connection).
 </Tab>
 <Tab heading="Consul UI" group="ui">
 

@@ -697,7 +697,7 @@ You can configure the following parameters in the `EnvoyExtensions` block:
 
 ### `Destination[]`
 
-Configures the destination for service traffic through terminating gateways. Refer to [Terminating Gateway](/consul/docs/connect/terminating-gateway) for additional information. 
+Configures the destination for service traffic through terminating gateways. Refer to [Terminating Gateway](/consul/docs/connect/gateways/terminating-gateway) for additional information. 
 
 You can configure the following parameters in the `Destination` block:
 
@@ -1082,7 +1082,7 @@ You can configure the following parameters in the `EnvoyExtensions` block:
 
 ### `spec.destination`
 
-Map of configurations that specify one or more destinations for service traffic routed through terminating gateways. Refer to [Terminating Gateway](/consul/docs/connect/terminating-gateway) for additional information. 
+Map of configurations that specify one or more destinations for service traffic routed through terminating gateways. Refer to [Terminating Gateway](/consul/docs/connect/gateways/terminating-gateway) for additional information. 
 
 #### Values
 

@@ -499,9 +499,9 @@ When using cluster peering connections, intentions secure your deployments with
       type: 'string: ""',
       description: {
         hcl:
-          "Specifies the [peer](/consul/docs/connect/cluster-peering/index.mdx) of the source service. `Peer` is mutually exclusive with `Partition`.",
+          "Specifies the [peer](/consul/docs/connect/cluster-peering) of the source service. `Peer` is mutually exclusive with `Partition`.",
         yaml:
-          "Specifies the [peer](/consul/docs/connect/cluster-peering/index.mdx) of the source service. `peer` is mutually exclusive with `partition`.",
+          "Specifies the [peer](/consul/docs/connect/cluster-peering) of the source service. `peer` is mutually exclusive with `partition`.",
       },
     },
     {

@@ -7,7 +7,7 @@ description: >-
 
 # Consul Dataplane CLI Reference
 
-The `consul-dataplane` command interacts with the binary for [simplified service mesh with Consul Dataplane](/consul/docs/k8s/dataplane). Use this command to install Consul Dataplane, configure its Envoy proxies, and secure Dataplane deployments.
+The `consul-dataplane` command interacts with the binary for [simplified service mesh with Consul Dataplane](/consul/docs/connect/dataplane). Use this command to install Consul Dataplane, configure its Envoy proxies, and secure Dataplane deployments.
 
 ## Usage
 

@@ -435,7 +435,7 @@ Specifies rule for rewriting the URL of incoming requests when an incoming reque
 
 ### Rules[].Filters.URLRewrite.Path
 
-Specifies a path that determines how Consul API Gateway rewrites a URL path. Refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage#reroute-http-requests) for additional information.
+Specifies a path that determines how Consul API Gateway rewrites a URL path. Refer to [Reroute HTTP requests](/consul/docs/api-gateway/usage/reroute-http-requests) for additional information.
 
 #### Values
 

@@ -111,7 +111,7 @@ If TLS is enabled on Consul, you will also need to add the following environment
 
 - [`CONSUL_CACERT`](/consul/commands#consul_cacert)
 - [`CONSUL_CLIENT_CERT`](/consul/commands#consul_client_cert)
-- [`CONSUL_CLIENT_KEY`](//consulcommands#consul_client_key)
+- [`CONSUL_CLIENT_KEY`](/consul/commands#consul_client_key)
 - [`CONSUL_HTTP_SSL`](/consul/commands#consul_http_ssl)
 
 ## Bootstrap Configuration
@@ -194,7 +194,7 @@ The [Advanced Configuration](#advanced-configuration) section describes addition
 
 ### Bootstrap Envoy on Windows VMs
 
-> Complete the [Connect Services on Windows Workloads to Consul Service Mesh tutorial](https://consul.io/consu/tutorials/consul-windows-workloads?utm_source=docs) to learn how to deploy Consul and use its service mesh on Windows VMs.
+> Complete the [Connect Services on Windows Workloads to Consul Service Mesh tutorial](/consul/tutorials/developer-mesh/consul-windows-workloads) to learn how to deploy Consul and use its service mesh on Windows VMs.
 
 If you are running Consul on a Windows VM, attempting to bootstrap Envoy with the `consul connect envoy` command returns the following output:
 

@@ -138,7 +138,7 @@ documentation for details about supported configuration parameters.
 
 ### Service Discovery
 
-Proxies can use Consul's [service discovery API](https://consul.io/%60/v1/health/connect/:service_id%60) to return all available, Connect-capable endpoints for a given service. This endpoint supports a `cached` query parameter, which uses [agent caching](/consul/api-docs/features/caching) to improve
+Proxies can use Consul's [service discovery API](/consul/api-docs/health#list-service-instances-for-connect-enabled-service) to return all available, Connect-capable endpoints for a given service. This endpoint supports a `cached` query parameter, which uses [agent caching](/consul/api-docs/features/caching) to improve
 performance. The API package provides a [`UseCache`] query option to leverage caching.
 In addition to performance improvements, using the cache makes the mesh more resilient to Consul server outages. This is because the mesh "fails static" with the last known set of service instances still used, rather than errors on new connections.
 

@@ -108,8 +108,9 @@ The following table describes the required input variables for the `acl-controll
 | `name_prefix`                       | string   | AWS resources created by the `acl-controller` module will include this prefix in the resource name.                                                                                                                                        |
 
 <EnterpriseAlert>
-If you are using Consul Enterprise, see <a href="/docs/ecs/enterprise#admin-partitions-and-namespaces">Admin Partitions and Namespaces</a> for
-additional configuration required to support Consul Enterprise on ECS.
+
+If you are using Consul Enterprise, see the [Admin Partitions and Namespaces requirements documentation](/consul/docs/ecs/requirements) for additional configuration required to support Consul Enterprise on ECS.
+
 </EnterpriseAlert>
 
 ## Deploy your services

@@ -138,7 +138,7 @@ When a customer deploys new clusters to a 1.10.0+ent release, they need to have
 
 New Consul cluster deployments using 1.10.0+ent will need to have a valid license on servers to successfully deploy.
 This valid license must be on-disk (auto-loaded) or as an environment variable.
-Please see the [upgrade requirements](https://consul.io/faq#q-what-are-the-upgrade-requirements).
+Please see the [upgrade requirements](/consul/docs/enterprise/license/faq#q-what-are-the-upgrade-requirements).
 
 ## Q: What is the migration path for customers who want to migrate from their existing license-as-applied-via-the-CLI flow to the license on disk flow?
 
@@ -183,7 +183,7 @@ When downgrading to a version of Consul before 1.10.0+ent, customers will need t
 
 ## Q: Are there potential pitfalls when downgrading or upgrading Consul server instances?
 
-~> Verify that you meet the [upgrade requirements](https://consul.io/faq#q-what-are-the-upgrade-requirements).
+~> Verify that you meet the [upgrade requirements](/consul/docs/enterprise/license/faq#q-what-are-the-upgrade-requirements).
 
 Assume a scenario where there are three Consul server nodes:
 

@@ -34,7 +34,7 @@ or via a configuration file:
 
 ## Auto-join with Network Segments <EnterpriseAlert inline />
 
-In order to use cloud auto-join with [Network Segments](/consul/docs/enterprise/network-segments),
+In order to use cloud auto-join with [Network Segments](/consul/docs/enterprise/network-segments/network-segments-overview),
 you must reconfigure the Consul agent's Serf LAN port to match that of the
 segment you wish to join.