luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

peering: update docs with exposing servers (#14191)

This commit is contained in:
Nitya Dhanushkodi 2022-08-12 11:22:41 -07:00 committed by GitHub
parent 7bcdd59714
commit 558837dcc6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/content/docs/connect/cluster-peering/k8s.mdx
View File

@ -23,8 +23,7 @@ The following CRDs are used to create and manage a peering connection:
You must implement the following requirements to create and use cluster peering connections with Kubernetes: You must implement the following requirements to create and use cluster peering connections with Kubernetes:
- Consul version 1.13.1 or later - Consul version 1.13.1 or later
- At least two Kubernetes clusters - At least two Kubernetes clusters
- The Kubernetes clusters must be running in a flat network - The installation must be running on Consul on Kubernetes version 0.47.1 or later
- The network must be running on Consul on Kubernetes version 0.47.0 or later
### Helm chart configuration ### Helm chart configuration
@ -48,14 +47,19 @@ To establish cluster peering through Kubernetes, deploy clusters with the follow
</CodeBlockConfig> </CodeBlockConfig>
Install Consul on Kubernetes on each Kubernetes cluster by applying `values.yaml` using the Helm CLI. Install Consul on Kubernetes on each Kubernetes cluster by applying `values.yaml` using the Helm CLI. With these values,
the servers in each cluster will be exposed over a Kubernetes Load balancer service. This service can be customized
using [`server.exposeService`](/docs/k8s/helm#v-server-exposeservice). When generating a peering token from one of the
clusters, the address(es) of the load balancer will be used in the peering token, so the peering stream will go through
the load balancer in front of the servers. For customizing the addresses used in the peering token, see
[`global.peering.tokenGeneration`](/docs/k8s/helm#v-global-peering-tokengeneration).
```shell-session ```shell-session
$ export HELM_RELEASE_NAME=cluster-name $ export HELM_RELEASE_NAME=cluster-name
``` ```
```shell-session ```shell-session
$ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.47.0" --values values.yaml $ helm install ${HELM_RELEASE_NAME} hashicorp/consul --version "0.47.1" --values values.yaml
``` ```
## Create a peering token ## Create a peering token

4
website/content/docs/k8s/helm.mdx
View File

@ -73,7 +73,9 @@ Use these links to navigate to a particular top-level stanza.
- `source` ((#v-global-peering-tokengeneration-serveraddresses-source)) (`string: ""`) - Source can be set to "","consul" or "static". - `source` ((#v-global-peering-tokengeneration-serveraddresses-source)) (`string: ""`) - Source can be set to "","consul" or "static".
"" is the default source. If servers are enabled, it will check if `server.exposeService` is enabled, and read "" is the default source. If servers are enabled, it will check if `server.exposeService` is enabled, and read
the addresses from that service to use as the peering token server addresses. the addresses from that service to use as the peering token server addresses. If using admin partitions and
only Consul client agents are enabled, the addresses in `externalServers.hosts` and `externalServers.grpcPort`
will be used.
"consul" will use the Consul advertise addresses in the peering token. "consul" will use the Consul advertise addresses in the peering token.