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

Jump to bottom

Backport of Documentation update: Adding K8S clusters to external Consul servers into release/1.15.x #16380

Merged
merged 4 commits into from
Feb 22, 2023
Merged

Backport of Documentation update: Adding K8S clusters to external Consul servers into release/1.15.x #16380

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a07a868
backport of commit 7281e9c2d2a83853587db458d35c49fe366f5fc5
Ranjandas Feb 16, 2023
da34325
backport of commit bb2b8535943112c5cd317da4e25c253da6ddc60f
Ranjandas Feb 16, 2023
472d4b6
backport of commit de5485371425bd0da323ff4577a3c69fed4d8107
Ranjandas Feb 16, 2023
39d9fda
backport of commit 505b8e1e28f22fb6716ec3b99271a477f082967a
Ranjandas Feb 16, 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
18 changes: 9 additions & 9 deletions website/content/docs/k8s/deployment-configurations/servers-outside-kubernetes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,11 @@
---
layout: docs
page_title: Join External Servers to Consul on Kubernetes
page_title: Join Kubernetes Clusters to external Consul Servers
description: >-
Client agents that run on Kubernetes pods can join existing clusters whose server agents run outside of k8s. Learn how to expose gossip ports and bootstrap ACLs by configuring the Helm chart.
Kubernetes clusters can be joined to existing Consul clusters in a much simpler way with the introduction of Consul Dataplane. Learn how to add Kubernetes Clusters into an existing Consul cluster and bootstrap ACLs by configuring the Helm chart.
---

# Join External Servers to Consul on Kubernetes
# Join Kubernetes Clusters to external Consul Servers

If you have a Consul cluster already running, you can configure your
Consul on Kubernetes installation to join this existing cluster.
Expand All @@ -14,9 +14,7 @@ The below `values.yaml` file shows how to configure the Helm chart to install
Consul so that it joins an existing Consul server cluster.

The `global.enabled` value first disables all chart components by default
so that each component is opt-in. This allows us to _only_ setup the client
agents. We then opt-in to the client agents by setting `client.enabled` to
`true`.
so that each component is opt-in.

Next, configure `externalServers` to point it to Consul servers.
The `externalServers.hosts` value must be provided and should be set to a DNS, an IP,
Expand All @@ -37,8 +35,10 @@ externalServers:

</CodeBlockConfig>

**Note:** To join Consul on Kubernetes to an existing Consul server cluster running outside of Kubernetes,
refer to [Consul servers outside of Kubernetes](/consul/docs/k8s/deployment-configurations/servers-outside-kubernetes).
With the introduction of [Consul Dataplane](/consul/docs/connect/dataplane#what-is-consul-dataplane), Consul installation on Kubernetes is simplified by removing the Consul Client agents.
This requires the Helm installation and rest of the consul-k8s components installed on Kubernetes to talk to Consul Servers directly on various ports.
Before starting the installation, ensure that the Consul Servers are configured to have the gRPC port enabled `8502/tcp` using the [`ports.grpc = 8502`](/consul/docs/agent/config/config-files#grpc) configuration option.


## Configuring TLS

Expand Down Expand Up @@ -68,7 +68,7 @@ externalServers:
</CodeBlockConfig>

If your HTTPS port is different from Consul's default `8501`, you must also set
`externalServers.httpsPort`.
`externalServers.httpsPort`. If the Consul servers are not running TLS enabled, use this config to set the HTTP port the servers are configured with (default `8500`).

## Configuring ACLs

Expand Down