From 41dfa896534756bb74cb8c35d7291e7f3b6b77dd Mon Sep 17 00:00:00 2001 From: Nathan Coleman Date: Mon, 17 Oct 2022 16:45:18 -0400 Subject: [PATCH] Add note about current ServiceResolver requirement ServiceResolver may eventually be created implicitly by the API gateway controller, but that decision is pending. --- website/content/docs/api-gateway/configuration/meshservice.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/website/content/docs/api-gateway/configuration/meshservice.mdx b/website/content/docs/api-gateway/configuration/meshservice.mdx index c1e6f01d27..dcb1e6f9f8 100644 --- a/website/content/docs/api-gateway/configuration/meshservice.mdx +++ b/website/content/docs/api-gateway/configuration/meshservice.mdx @@ -35,5 +35,8 @@ Specifies the name of the service in the Consul service mesh to send traffic to. ### peer Specifies the name of the Consul peer exporting the service. If not specified, the service is assumed to be in the local datacenter. + +Note that a [ServiceResolver](/docs/connect/config-entries/service-resolver) is also required for the referenced Consul service indicating what peer the service is exported by. + * Type: string * Required: optional