lookup tailscale-operator-testing.tail0225ab.ts.net on 127.0.0.53:53: no such host;

Open
#173 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions, helm, kubernetes
Domain
ci-cd, devops, networking

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.

Description

needs-triage
  1. 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.

  1. 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

Dominant language
TypeScript
Stars
938
Forks
137
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tailscale/github-action

All issues in tailscale/github-action

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.