diff --git a/docs/docs/reference/networking/tailscale-policy.md b/docs/docs/reference/networking/tailscale-policy.md index 8542dab..9e9c784 100644 --- a/docs/docs/reference/networking/tailscale-policy.md +++ b/docs/docs/reference/networking/tailscale-policy.md @@ -6,8 +6,8 @@ description: Tailnet identity, policy file location, tags, and the credentials t # Tailscale policy The tailnet policy file is the canonical definition of tag ownership, -auto-approved subnet routes, network access rules, and Tailscale SSH access. It -is applied by CI, not by hand; +auto-approved subnet routes, node attributes, network access rules, and +Tailscale SSH access. It is applied by CI, not by hand; [ADR-0002](../../decisions/0002-manage-tailscale-policy-with-gitops.md) records why. To change it, follow the [policy change runbook](../../runbooks/tailscale-policy-change.md). @@ -114,6 +114,18 @@ hosts cannot use the split-DNS resolver `10.10.10.1` for `glab.lol` and `lab.gilman.io`. Admin-owned devices still reach dntls hosts through `autogroup:admin` → `*:*`. +## Node attributes + +| Target | Attribute | Effect | +| --- | --- | --- | +| `studio-1` (`100.122.142.76`) | `funnel` | Studio may run [Tailscale Funnel](https://tailscale.com/docs/features/tailscale-funnel) | + +The attribute targets the `studio-1` host alias, so only Studio can start a +funnel; Studio stays user-owned and untagged. The attribute permits Funnel but +exposes nothing by itself: a service becomes publicly reachable only while +`tailscale funnel` is serving it on Studio. Funnel also needs tailnet HTTPS +certificates, which are enabled. + ## Credentials CI authenticates with a Tailscale diff --git a/docs/docs/runbooks/tailscale-policy-change.md b/docs/docs/runbooks/tailscale-policy-change.md index e978c98..97b1048 100644 --- a/docs/docs/runbooks/tailscale-policy-change.md +++ b/docs/docs/runbooks/tailscale-policy-change.md @@ -6,7 +6,8 @@ description: Change, verify, roll back, or emergency-edit the tailnet policy fil # Change the Tailscale policy Use this runbook to change the tailnet policy file: tags, auto-approved routes, -access rules, or Tailscale SSH access. Field-level facts live in the +node attributes, access rules, or Tailscale SSH access. Field-level facts live +in the [Tailscale policy reference](../reference/networking/tailscale-policy.md). ## Preconditions