mirror of
https://github.com/netbirdio/docs.git
synced 2026-09-18 21:09:04 +02:00
Reference the config-file bootstrap workflow from install and peer pages (#868)
* Reference the config-file bootstrap workflow from install and peer pages Link Bootstrap peers via config file from the setup-key sections of the Linux, Windows, macOS, and Docker install pages, from the Setup Keys page, and from the Kubernetes routing-peers guide. The page was only reachable from the sidebar, so this surfaces the unattended deployment workflow where headless and at-scale enrollment is already discussed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Clarify the Kubernetes example demonstrates setup-key enrollment The manifest passes a setup key but does not mount a pre-populated config, so reword the cross-link: the example enrolls with a setup key, and the bootstrap guide covers the additional config-file step. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 4.8
parent
a6c4910479
commit
b37befc602
@@ -329,6 +329,8 @@ Check connection status:
|
||||
In case you are activating a server peer, you can use a [setup key](/manage/peers/register-machines-using-setup-keys) as described in the steps below.
|
||||
> This is especially helpful when you are running multiple server instances with infrastructure-as-code tools like ansible and terraform.
|
||||
|
||||
For unattended deployments across many machines, pre-populate the client config so each peer registers on first start. See [Bootstrap peers via config file](/manage/peers/bootstrap-via-config-file).
|
||||
|
||||
1. Login to the Management Service. You need to have a `setup key` in hand (see [setup keys](/manage/peers/register-machines-using-setup-keys)).
|
||||
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user