tailscale / tailscale/github-action
PSA: make sure to allow your CI to access your DNS server inside the Tailscale ACL
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
I was having issues with DNS solving.
The reason was that I didn't allow the "tag:ci" to allow my custom DNS server inside my ACL (it drops everything by default).
(I am using MagicDNS + a CoreDNS server running inside Kubernetes)
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.
Research direction
The issue names no file, test, or entry point. First identify where CI connectivity or Tailscale ACL guidance belongs, then document access for the tag:ci identity to the custom DNS server and verify the guidance against MagicDNS, CoreDNS, and Kubernetes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, kubernetes
- Domain
- ci-cd, infrastructure, networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100