Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport of First cluster grpc service should be NodePort for the second cluster to connect into release/1.15.x #16653

Merged
merged 4 commits into from
Mar 16, 2023
Merged

Backport of First cluster grpc service should be NodePort for the second cluster to connect into release/1.15.x #16653

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
46748de
backport of commit 9dc24ffd1bf307c40cea44cd3bc294939a1532a7
vjwilson1987 Feb 25, 2023
1aa5176
backport of commit 2fa4ae4d6af084c2ce49316ccadf215a455a90b9
vjwilson1987 Mar 4, 2023
039c897
backport of commit 7cccb2e1fe058a5d05f62be59452d4405963120b
vjwilson1987 Mar 4, 2023
5eb67ec
backport of commit 1442c12573c4473590f9225ceb29d89edf4c2fa1
vjwilson1987 Mar 4, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,6 +50,17 @@ global:
gossipEncryption:
secretName: consul-gossip-encryption-key
secretKey: key
server:
exposeService:
enabled: true
type: NodePort
nodePort:
## all are random nodePorts and you can set your own
http: 30010
https: 30011
serf: 30012
rpc: 30013
grpc: 30014
ui:
service:
type: NodePort
Expand All @@ -65,6 +76,8 @@ 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.

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.

```shell-session
Expand Down Expand Up @@ -123,6 +136,8 @@ externalServers:
hosts: ["10.0.0.4"]
# The node port of the UI's NodePort service or the load balancer port.
httpsPort: 31557
# Matches the gRPC port of the Consul servers in the first cluster.
grpcPort: 30014
tlsServerName: server.dc1.consul
# The address of the kube API server of this Kubernetes cluster
k8sAuthMethodHost: https://kubernetes.example.com:443
Expand All @@ -147,6 +162,8 @@ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cluster1-consul-ui NodePort 10.0.240.80 <none> 443:31557/TCP 40h
```

The `grpcPort: 30014` configuration refers to the gRPC port number specified in the `NodePort` configuration in the first cluster.

Set the `externalServer.tlsServerName` to `server.dc1.consul`. This the DNS SAN
(Subject Alternative Name) that is present in the Consul server's certificate.
This is required because the connection to the Consul servers uses the node IP,
Expand Down