hashicorp · trujillo-adam · Sep 7, 2023 · Jun 28, 2023 · Jun 28, 2023 · Jun 28, 2023
@@ -639,7 +639,7 @@ The `/agent/service/register` endpoint supports camel case and _snake case_ for
 
 - `Proxy` `(Proxy: nil)` - From 1.2.3 on, specifies the configuration for a
   service mesh proxy instance. This is only valid if `Kind` defines a proxy or gateway.
-  See the [Proxy documentation](/consul/docs/connect/registration/service-registration)
+  Refer to the [Service mesh proxy configuration reference](/consul/docs/connect/proxies/proxy-config-reference)
   for full details.
 
 - `Connect` `(Connect: nil)` - Specifies the
@@ -698,8 +698,8 @@ For the `Connect` field, the parameters are:
   Managed proxies (which have been deprecated since Consul v1.3.0) have been 
   [removed](/consul/docs/connect/proxies) since v1.6.0.
 - `SidecarService` `(ServiceDefinition: nil)` - Specifies an optional nested
-  service definition to register. For more information see
-  [Sidecar Service Registration](/consul/docs/connect/registration/sidecar-service).
+  service definition to register. Refer to 
+  [Deploy sidecar services](/consul/docs/connect/proxies/deploy-sidecar-services) for additional information.
 
 ### Sample Payload
 

@@ -57,10 +57,8 @@ The table below shows this endpoint's support for
 - `compile-dc` `(string: "")` - Specifies the datacenter to use as the basis of
   compilation. This will default to the datacenter of the agent being queried.
 
-  This value comes from an [upstream
-  configuration](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
-  [`datacenter`](/consul/docs/connect/registration/service-registration#datacenter)
-  parameter.
+  This value comes from the `datacenter` parameter in an [upstream
+  configuration](/consul/docs/connect/proxies/proxy-config-reference#upstream-configuration-reference).
 
 - `ns` `(string: "")` <EnterpriseAlert inline /> - Specifies the source namespace you use as the basis of compilation.
   You can also [specify the namespace through other methods](#methods-to-specify-namespace).
@@ -71,11 +69,8 @@ The table below shows this endpoint's support for
   timeout](/consul/docs/connect/config-entries/service-resolver#connecttimeout) for
   any service resolved in the compiled chain.
 
-  This value comes from the `connect_timeout_ms` key in an [upstream
-  configuration](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
-  opaque
-  [`config`](/consul/docs/connect/registration/service-registration#config-1)
-  parameter.
+  This value comes from the `connect_timeout_ms` key in the opaque `config` field of the [upstream
+  configuration](/consul/docs/connect/proxies/proxy-config-reference#upstream-configuration-reference).
 
 - `OverrideProtocol` `(string: "")` - Overrides the final
   [protocol](/consul/docs/connect/config-entries/service-defaults#protocol) used in
@@ -86,23 +81,17 @@ The table below shows this endpoint's support for
   would be L7 and TCP is passed here the chain will not include Routers or
   Splitters.
 
-  This value comes from the `protocol` key in an [upstream
-  configuration](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
-  opaque
-  [`config`](/consul/docs/connect/registration/service-registration#config-1)
-  parameter.
+  This value comes from the `protocol` key in an opaque `config` field of the [upstream
+  configuration](/consul/docs/connect/proxies/proxy-config-reference#upstream-configuration-reference).
 
 - `OverrideMeshGateway` `(MeshGatewayConfig: <optional>)` - Overrides the final
   [mesh gateway configuration](/consul/docs/connect/gateways/mesh-gateway#connect-proxy-configuration)
   for this any service resolved in the compiled chain.
 
-  This value comes from either the [proxy
-  configuration](/consul/docs/connect/registration/service-registration#complete-configuration-example)
-  [`mesh_gateway`](/consul/docs/connect/registration/service-registration#mesh_gateway)
-  parameter or an [upstream
-  configuration](/consul/docs/connect/registration/service-registration#upstream-configuration-reference)
-  [`mesh_gateway`](/consul/docs/connect/registration/service-registration#mesh_gateway-1)
-  parameter. If both are present the value defined on the upstream is used.
+  This value comes from the `mesh_gateway` parameter in either the [proxy
+  configuration](/consul/docs/connect/proxies/proxy-config-reference#proxy-parameters) or [upstream
+  configuration](/consul/docs/connect/proxies/proxy-config-reference#upstream-configuration-reference)
+  If both parameters are configured, Consul uses the value defined on the upstream.
 
   - `Mode` `(string: "")` - One of `none`, `local`, or `remote`.
 

@@ -36,7 +36,7 @@ Usage: `consul connect envoy [options] [-- pass-through options]`
 
 #### Envoy Options for both Sidecars and Gateways
 
-- `-proxy-id` - The [proxy service](/consul/docs/connect/registration/service-registration) ID.
+- `-proxy-id` - The [proxy service](/consul/docs/connect/proxies/proxy-config-reference) ID.
   This service ID must already be registered with the local agent unless a gateway is being
   registered with the `-register` flag. As of Consul 1.8.0, this can also be
   specified via the `CONNECT_PROXY_ID` environment variable.
@@ -133,7 +133,7 @@ compatibility with Envoy and prevent potential issues. Default is `false`.
 - `-sidecar-for` - The _ID_ (not name if they differ) of the service instance
   this proxy will represent. The target service doesn't need to exist on the
   local agent yet but a [sidecar proxy
-  registration](/consul/docs/connect/registration/service-registration) with
+  registration](/consul/docs/proxies/deploy-sidecar-services) with
   `proxy.destination_service_id` equal to the passed value must be present. If
   multiple proxy registrations targeting the same local service instance are
   present the command will error and `-proxy-id` should be used instead.
@@ -225,9 +225,9 @@ proxy configuration needed.
 
 ## Examples
 
-Assume a local service instance is registered on the local agent with a
+In the following examples, a local service instance is registered on the local agent with a
 sidecar proxy (using the [sidecar service
-registration](/consul/docs/connect/registration/service-registration) helper) as below.
+registration](/consul/docs/connect/proxies/deploy-sidecar-services) helper):
 
 ```hcl
 service {

@@ -24,14 +24,14 @@ Usage: `consul connect proxy [options]`
 - `-sidecar-for` - The _ID_ (not name if they differ) of the service instance
   this proxy will represent. The target service doesn't need to exist on the
   local agent yet but a [sidecar proxy
-  registration](/consul/docs/connect/registration/service-registration) with
+  registration](/consul/docs/connect/proxies/deploy-sidecar-services) with
   `proxy.destination_service_id` equal to the passed value must be present. If
   multiple proxy registrations targeting the same local service instance are
   present the command will error and `-proxy-id` should be used instead.
   This can also be specified via the `CONNECT_SIDECAR_FOR` environment variable.
 
 - `-proxy-id` - The [proxy
-  service](/consul/docs/connect/registration/service-registration) ID on the
+  service](/consul/docs/connect/proxies/proxy-config-reference) ID on the
   local agent. This must already be present on the local agent. This option
   can also be specified via the `CONNECT_PROXY_ID` environment variable.
 

@@ -38,7 +38,7 @@ Usage: `consul connect redirect-traffic [options]`
 
 - `-consul-dns-port` - The port of the Consul DNS resolver. If provided, DNS queries will be redirected to the provided IP address for name resolution.
 
-- `-proxy-id` - The [proxy service](/consul/docs/connect/registration/service-registration) ID.
+- `-proxy-id` - The [proxy service](/consul/docs/connect/proxies/proxy-config-reference) ID.
   This service ID must already be registered with the local agent.
 
 - `-proxy-inbound-port` - The inbound port that the proxy is listening on.

@@ -637,16 +637,16 @@ Refer to the [formatting specification](https://golang.org/pkg/time/#ParseDurati
   - `server` ((#server_rpc_port)) - Server RPC address. Default 8300. TCP
     only.
   - `sidecar_min_port` ((#sidecar_min_port)) - Inclusive minimum port number
-    to use for automatically assigned [sidecar service registrations](/consul/docs/connect/registration/sidecar-service).
+    to use for automatically assigned [sidecar service registrations](/consul/docs/connect/proxies/deploy-sidecar-services).
     Default 21000. Set to `0` to disable automatic port assignment.
   - `sidecar_max_port` ((#sidecar_max_port)) - Inclusive maximum port number
-    to use for automatically assigned [sidecar service registrations](/consul/docs/connect/registration/sidecar-service).
+    to use for automatically assigned [sidecar service registrations](/consul/docs/connect/proxies/deploy-sidecar-services).
     Default 21255. Set to `0` to disable automatic port assignment.
   - `expose_min_port` ((#expose_min_port)) - Inclusive minimum port number
-    to use for automatically assigned [exposed check listeners](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference).
+    to use for automatically assigned [exposed check listeners](/consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference).
     Default 21500. Set to `0` to disable automatic port assignment.
   - `expose_max_port` ((#expose_max_port)) - Inclusive maximum port number
-    to use for automatically assigned [exposed check listeners](/consul/docs/connect/registration/service-registration#expose-paths-configuration-reference).
+    to use for automatically assigned [exposed check listeners](/consul/docs/connect/proxies/proxy-config-reference#expose-paths-configuration-reference).
     Default 21755. Set to `0` to disable automatic port assignment.
 
 - `primary_datacenter` - This designates the datacenter

@@ -64,7 +64,7 @@ Refer to [mesh gateway modes](/consul/docs/connect/gateways/mesh-gateway#modes)
 
 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.
+- Configure the `proxy.upstreams` parameters to route traffic to the correct service, namespace, and peer. Refer to the [`upstreams`](/consul/docs/connect/proxies/proxy-config-reference#upstream-configuration-reference) documentation for details.
 - The `proxy.upstreams.destination_name` parameter is always required.
 - The `proxy.upstreams.destination_peer` parameter must be configured to enable cross-cluster traffic.
 - The `proxy.upstream/destination_namespace` configuration is only necessary if the destination service is in a non-default namespace.