Tailscale Services integration
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- authentication
Research direction
The issue does not name any files or tests. Start by reviewing tsidp's startup and flag handling alongside the linked Tailscale Services and svcid documentation, then determine the required behavior for shared service references, instance access, and ephemeral nodes. Done would require an agreed design and an explicit implementation scope.
Written by the indexing model from the issue text.
Description
Just seen the Tailscale Services announcement and I wonder what would be the easiest way to integrate TSIDP with this to provide high availability.
My understanding is that we would have to:
- modify
tsidpto add a new flag with service reference and bind to that service on startup; - run a number of the
tsidpinstances across different locations within the same tailnet, using the same service reference.
If using svcid, the FQDN of TSIDP kind of does not make sense because everybody should be using the service FQDN, so accessing the individual instance of tsidp should be redirecting to the service URL automatically or giving error. Also, these tsidp nodes could be ephemeral, not even having any name?
Any thoughts? Is my understanding correct? Should we do something like this?
- Dominant language
- Go
- Stars
- 669
- Forks
- 61
- Avg merge
- 6d 6h
- Merged PRs (30d)
- 3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tailscale/tsidp
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Groups claim Open
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100