starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-11 20:00:28 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Feature] IP pool #1160

New Issue
Open
opened 2025-12-29 02:28:37 +01:00 by adam · 0 comments
adam commented 2025-12-29 02:28:37 +01:00
Owner
Copy Link

Originally created by @Tillerino on GitHub (Nov 22, 2025).

Use case

Tailscale has had the IP pool feature in beta for a while now. I was wondering if there is interest to implement this at all and if it would be implemented before it leaves beta in tailscale.

Description

    {
        "grants": ["..."],
        "nodeAttrs": [
            {
                "target": ["autogroup:admin"],
                "ipPool": ["100.81.0.0/16"],
            },
            {
                "target": ["group:dev"],
                "ipPool": ["100.85.0.0/16"],
            },
        ],
    }

The way that I understand the feature, you can make sure that certain nodes receive IPs from subranges within your IP prefix. In the example (copied from the linked doc), IP pools are only assigned to groups. I don't know which targets would be valid here. I am also not certain if new devices that are not in one of those groups are guaranteed to receive IPs from outside of those pools, though that would certainly make sense.

Contribution

  • I can write the design doc for this feature
  • I can contribute this feature

How can it be implemented?

No response

Originally created by @Tillerino on GitHub (Nov 22, 2025). ### Use case Tailscale has had the [IP pool](https://tailscale.com/kb/1304/ip-pool) feature in beta for a while now. I was wondering if there is interest to implement this at all and if it would be implemented before it leaves beta in tailscale. ### Description ```yaml { "grants": ["..."], "nodeAttrs": [ { "target": ["autogroup:admin"], "ipPool": ["100.81.0.0/16"], }, { "target": ["group:dev"], "ipPool": ["100.85.0.0/16"], }, ], } ``` The way that I understand the feature, you can make sure that certain nodes receive IPs from subranges within your IP prefix. In the example (copied from the linked doc), IP pools are only assigned to groups. I don't know which targets would be valid here. I am also not certain if new devices that are _not_ in one of those groups are guaranteed to receive IPs from _outside_ of those pools, though that would certainly make sense. ### Contribution - [x] I can write the design doc for this feature - [x] I can contribute this feature ### How can it be implemented? _No response_
adam added the enhancement label 2025-12-29 02:28:37 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#1160
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?