From e5faef344c4a678e2dbaee33812f4d653adcedd1 Mon Sep 17 00:00:00 2001 From: Tim Gross Date: Thu, 28 Mar 2024 15:10:20 -0400 Subject: [PATCH] note we don't need upstream service port, either --- website/content/docs/integrations/consul/service-mesh.mdx | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/website/content/docs/integrations/consul/service-mesh.mdx b/website/content/docs/integrations/consul/service-mesh.mdx index 43898130f19..2b37184b4ca 100644 --- a/website/content/docs/integrations/consul/service-mesh.mdx +++ b/website/content/docs/integrations/consul/service-mesh.mdx @@ -237,7 +237,7 @@ job "countdash" { driver = "docker" env { - COUNTING_SERVICE_URL = "http://count-api.virtual.consul:9001" + COUNTING_SERVICE_URL = "http://count-api.virtual.consul" } config { @@ -353,12 +353,14 @@ environment variable `$COUNTING_SERVICE_URL`: ```hcl env { - COUNTING_SERVICE_URL = "http://count-api.virtual.consul:9001" + COUNTING_SERVICE_URL = "http://count-api.virtual.consul" } ``` The `transparent_proxy` block ensures that DNS queries are made to Consul so -that the `count-api.virtual.consul` name resolves to a virtual IP address. +that the `count-api.virtual.consul` name resolves to a virtual IP address. Note +that you don't need to specify a port number because the virtual IP will only be +directed to the correct service port. ### Manually Configured Upstreams