Skip to content

Commit

Permalink
Update website/content/docs/k8s/deployment-configurations/single-dc-m…
Browse files Browse the repository at this point in the history 
…ulti-k8s.mdx

Co-authored-by: trujillo-adam <[email protected]>
  • Loading branch information
@vjwilson1987 @trujillo-adam
vjwilson1987 and trujillo-adam authored Mar 4, 2023
1 parent 9dc24ff commit 2fa4ae4
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -76,8 +76,7 @@ The UI's service type is set to be `NodePort`.
This is needed to connect to servers from another cluster without using the pod IPs of the servers,
which are likely going to change.

The other services, especially grpc is also set to be `NodePort` with a random nodePort. Here, it chose 30014.
This is needed to discover the consul servers using gRPC when connecting from another cluster.
Other services are exposed as `NodePort` services and configured with random port numbers. In this example, the `grpc` port is set to `30014`, which enables services to discover Consul servers using gRPC when connecting from another cluster.

To deploy, first generate the Gossip encryption key and save it as a Kubernetes secret.

Expand Down

0 comments on commit 2fa4ae4

Please sign in to comment.