From f7030513c15f5506e9e7559aaeea915cc37ad09a Mon Sep 17 00:00:00 2001 From: Todd Date: Wed, 8 Feb 2023 13:38:13 -0800 Subject: [PATCH] Update documentation to encourage using "hcp_boundary_cluster_id" (#2940) --- website/content/docs/configuration/worker/pki-worker.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/website/content/docs/configuration/worker/pki-worker.mdx b/website/content/docs/configuration/worker/pki-worker.mdx index a7d1966a0..6e5af467d 100644 --- a/website/content/docs/configuration/worker/pki-worker.mdx +++ b/website/content/docs/configuration/worker/pki-worker.mdx @@ -80,8 +80,9 @@ workers. These fields are only valid for [KMS Workers][]. `name` and # Multi-Hop WorkersHCP Only -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.