BREAKING
Routes
Route internals have been rewritten, removing the dedicated route table in the
database. This was done to simplify the codebase, which had grown unnecessarily
complex after the routes were split into separate tables. The overhead of having
to go via the database and keeping the state in sync made the code very hard to
reason about and prone to errors. The majority of the route state is only
relevant when headscale is running, and is now only kept in memory. As part of
this, the CLI and API has been simplified to reflect the changes;
$ headscale nodes list-routes
ID | Hostname | Approved | Available | Serving (Primary)
1 | ts-head-ruqsg8 | | 0.0.0.0/0, ::/0 |
2 | ts-unstable-fq7ob4 | | 0.0.0.0/0, ::/0 |
$ headscale nodes approve-routes --identifier 1 --routes 0.0.0.0/0,::/0
Node updated
$ headscale nodes list-routes
ID | Hostname | Approved | Available | Serving (Primary)
1 | ts-head-ruqsg8 | 0.0.0.0/0, ::/0 | 0.0.0.0/0, ::/0 | 0.0.0.0/0, ::/0
2 | ts-unstable-fq7ob4 | | 0.0.0.0/0, ::/0 |Note that if an exit route is approved (0.0.0.0/0 or ::/0), both IPv4 and IPv6
will be approved.
- Route API and CLI has been removed
#2422 - Routes are now managed via the Node API
#2422 - Only routes accessible to the node will be sent to the node
#2561
Policy v2
This release introduces a new policy implementation. The new policy is a
complete rewrite, and it introduces some significant quality and consistency
improvements. In principle, there are not really any new features, but some long
standing bugs should have been resolved, or be easier to fix in the future. The
new policy code passes all of our tests.
Changes
- The policy is validated and "resolved" when loading, providing errors for
invalid rules and conditions.- Previously this was done as a mix between load and runtime (when it was
applied to a node). - This means that when you convert the first time, what was previously a
policy that loaded, but failed at runtime, will now fail at load time.
- Previously this was done as a mix between load and runtime (when it was
- Error messages should be more descriptive and informative.
- There is still work to be here, but it is already improved with "typing"
(e.g. only Users can be put in Groups)
- There is still work to be here, but it is already improved with "typing"
- All users must contain an
@character.- If your user naturally contains and
@, like an email, this will just work. - If its based on usernames, or other identifiers not containing an
@, an
@should be appended at the end. For example, if your user isjohn, it
must be written asjohn@in the policy.
- If your user naturally contains and
Migration notes when the policy is stored in the database.
This section only applies if the policy is stored in the database and
Headscale 0.26 doesn't start due to a policy error
(failed to load ACL policy).
- Start Headscale 0.26 with the environment variable
HEADSCALE_POLICY_V1=1
set. You can check that Headscale picked up the environment variable by
observing this message during startup:Using policy manager version: 1 - Dump the policy to a file:
headscale policy get > policy.json - Edit
policy.jsonand migrate to policy V2. Use the command
headscale policy check --file policy.jsonto check for policy errors. - Load the modified policy:
headscale policy set --file policy.json - Restart Headscale without the environment variable
HEADSCALE_POLICY_V1.
Headscale should now print the messageUsing policy manager version: 2and
startup successfully.
SSH
The SSH policy has been reworked to be more consistent with the rest of the
policy. In addition, several inconsistencies between our implementation and
Tailscale's upstream has been closed and this might be a breaking change for
some users. Please refer to the
upstream documentation
for more information on which types are allowed in src, dst and users.
There is one large inconsistency left, we allow * as a destination as we
currently do not support autogroup:self, autogroup:member and
autogroup:tagged. The support for * will be removed when we have support for
the autogroups.
Current state
The new policy is passing all tests, both integration and unit tests. This does
not mean it is perfect, but it is a good start. Corner cases that is currently
working in v1 and not tested might be broken in v2 (and vice versa).
We do need help testing this code
Other breaking changes
- Disallow
server_urlandbase_domainto be equal
#2544 - Return full user in API for pre auth keys instead of string
#2542 - Pre auth key API/CLI now uses ID over username
#2542
Changes
- Use Go 1.24 #2427
- Add
headscale policy checkcommand to check policy
#2553 oidc.map_legacy_usersandoidc.strip_email_domainhas been removed
#2411- Add more information to
/debugendpoint
#2420- It is now possible to inspect running goroutines and take profiles
- View of config, policy, filter, ssh policy per node, connected nodes and
DERPmap
- OIDC: Fetch UserInfo to get EmailVerified if necessary
#2493- If a OIDC provider doesn't include the
email_verifiedclaim in its ID
tokens, Headscale will attempt to get it from the UserInfo endpoint.
- If a OIDC provider doesn't include the
- OIDC: Try to populate name, email and username from UserInfo
#2545 - Improve performance by only querying relevant nodes from the database for node
updates #2509 - node FQDNs in the netmap will now contain a dot (".") at the end. This aligns
with behaviour of tailscale.com
#2503 - Restore support for "Override local DNS"
#2438 - Add documentation for routes
#2496