tailscale / tailscale/github-action
lookup tailscale-operator-testing.tail0225ab.ts.net on 127.0.0.53:53: no such host;
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 938
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
- From github action
Run tailscale/github-action@v2
with:
oauth-client-id: ***
oauth-secret: ***
tags: tag:ci
kubeconfig configured for "tailscale-operator-testing"
helm upgrade --install persistent-test ./persistent-test
--namespace testing
--set database.enabled=true
--wait
--timeout=2m
--debug
Error: Kubernetes cluster unreachable: Get "https://tailscale-operator-testing.tail0225ab.ts.net/version": dial tcp: lookup tailscale-operator-testing.tail0225ab.ts.net on 127.0.0.53:53: no such host
This was working earlier today.
- Kubectl with the same command is fine when running from local machine:
tailscale configure kubeconfig tailscale-operator-testing
kubeconfig configured for "tailscale-operator-testing"
helm upgrade --install persistent-test ./persistent-test
--namespace testing
--set database.enabled=true
--wait
--timeout=2m
--debug
Release "persistent-test" has been upgraded. Happy Helming!
NAME: persistent-test
LAST DEPLOYED: Wed Apr 9 17:32:32 2025
NAMESPACE: testing
STATUS: deployed
REVISION: 48
TEST SUITE: None
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
Start with the workflow step invoking tailscale/github-action@v2 and the helm upgrade command shown in the report. Compare DNS and cluster reachability on the GitHub Actions runner with the local kubectl setup; done means the workflow can resolve the cluster endpoint and complete the Helm deployment reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, helm, kubernetes
- Domain
- ci-cd, devops, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100