CyberCoveLLC/threshold
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update documentation to encourage using "hcp_boundary_cluster_id" (#2940)

Browse Source
This commit is contained in:
Todd authored and GitHub committed 2023-02-08 13:38:13 -08:00
1 parent ffd59fa87a
commit f7030513c1
1 file changed
+3 -2
Download Patch File Download Diff File Expand all files Collapse all files
website/content/docs/configuration/worker/pki-worker.mdx
+3 -2
View File
@@ -80,8 +80,9 @@ workers. These fields are only valid for [KMS Workers][]. `name` and
# Multi-Hop Workers<sup>HCP Only</sup>
You can use the `initial_upstreams` field to configure PKI workers to either connect directly to the control plane
or to other workers, when set to the worker's `public_addr`.
You can use the `hcp_boundary_cluster_id` field to configure PKI workers to connect to your HCP
Boundary cluster or the `initial_upstreams` field to connect directly to other workers,
when set to that worker's `public_addr` field.
A multi-hop configuration is when two or more workers are connected, and there are multiple “hops” from a worker to
the controller. There are no limits on the amount of workers allowed in a multi-hop configuration.