webnet/tailscale
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

ipn/conf: support RemoteConfig in the config file

Browse Source 
Add ConfigVAlpha.RemoteConfig so a user-data/cloud-init config can
delegate remote control to the tailnet admin (see Prefs.RemoteConfig).

Updates #1866

Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com>
This commit is contained in:
Kristoffer Dalby
2026-07-14 10:29:19 +02:00
committed by Kristoffer Dalby
parent f9cd687180
commit 58fcaaf9a5
3 changed files with 33 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gokrazy/README.md
+3 -1
View File
@@ -92,7 +92,9 @@ single AMI supports two ways of joining a tailnet:
```
A config present in user-data locks the CLI (`tailscale set`/`up` are
rejected) unless it sets `"Locked": false`.
rejected) unless it sets `"Locked": false`. Add `"RemoteConfig": true` to
hand full remote management of the node to the tailnet admin (see
`Prefs.RemoteConfig`) — appropriate for admin-owned fleet devices.
- **Interactive (serial console):** launch the AMI with *no* user-data. The
`optional:` prefix means the missing config is not an error, so `tailscaled`