github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Apply suggestions from code review 

Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com>
pull/19755/head
Jeff Boruszak 2023-11-29 10:20:23 -08:00 committed by GitHub
parent bf1e4681b1
commit a762adee3c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/docs/install/ports.mdx
View File

@ -103,7 +103,7 @@ The following table lists information about the Consul API's gRPC with TLS port
| :----------- | :------- | :------------------ | :------- |
| `8503` | TCP | Enabled by default | `8502` |
This port receives incoming traffic from the dataplanes when using [Consul Dataplane](/consul/docs/connect/dataplane) instead of client agents. We recommend using `8503` as your conventional gRPC port number, as it allows some tools to work automatically.
This port receives incoming traffic from the dataplanes when using [Consul Dataplane](/consul/docs/connect/dataplane) instead of client agents. We recommend using `8503` as your conventional gRPC port number because it allows some tools to work automatically.
In deployments with [cluster peering connections](/consul/docs/connect/cluster-peering), this port provides incoming and outgoing access between remote server peers. Specifically, the dialing peer needs outgoing access and the accepting peer needs incoming access. The address dialed depends on whether or not the cluster peering connection uses mesh gateways and whether the mesh gateway is in remote or local mode:
@ -113,7 +113,7 @@ In deployments with [cluster peering connections](/consul/docs/connect/cluster-p
In both local and remote cases, incoming traffic comes from the mesh gateways.
When the [v2 catalog](/consul/docs/architecture/catalog/v2) is enabled, all API calls from external systems such as the Consul CLI and Terraform provider use this port.
When the [v2 catalog](/consul/docs/architecture/catalog/v2) is enabled, all API calls from external systems, such as the Consul CLI and Terraform provider, use this port.
### Server RPC
@ -127,7 +127,7 @@ This port sends and receives traffic between Consul servers in the same datacent
When using WAN federation without mesh gateways, incoming and outgoing traffic on this port is required between all federated servers.
When using WAN federation with mesh gateways, Consul servers must accept Server RPC requests from mesh gateways in the local datacenter, regardless of which mesh gateway mode is used. As a result, traffic always comes from a local mesh gateway.
When using WAN federation with mesh gateways, Consul servers must accept server RPC requests from mesh gateways in the local datacenter, regardless of which mesh gateway mode is used. As a result, traffic always comes from a local mesh gateway.
### LAN serf
@ -149,7 +149,7 @@ The following table lists information about the WAN serf port defaults:
| :----------- | :---------- | :----------------- | :------- |
| `8302` | TCP and UDP | Enabled by default | `8302` |
This port sends and receives traffic between Consul servers in a federated network. WAN-federated networks require one cluster to serve as the primary datacenter while the others function as secondary datacenters.
This port sends and receives traffic between Consul servers in a federated network. WAN-federated networks require one cluster to serve as the primary datacenter while the others function as secondary datacenters. Refer to [Enabling WAN Federation Control Plane Traffic](/consul/docs/connect/gateways/mesh-gateway/wan-federation-via-mesh-gateways) for additional information.
When using WAN federation without mesh gateways, incoming and outgoing traffic on this port is required between all federated servers.