anton-remote-access

Access a Kubernetes cluster remotely with talosctl and kubectl over Tailscale MagicDNS.

3|Updated May 13, 2025
One-click install
npx skills add https://github.com/wcygan/anton --skill anton-remote-access
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anton-remote-access
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/anton-remote-access
Command: npx skills add https://github.com/wcygan/anton --skill anton-remote-access

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remote access to Anton's Kubernetes cluster from off-LAN using talosctl, kubectl, and Tailscale MagicDNS.

Core Features & Use Cases

  • LAN and Tailnet-based access paths to reach cluster nodes from a remote workstation.
  • Guidance on using talosctl and kubectl with the generated talosconfig and kubeconfig.
  • Security tips, context management, and troubleshooting steps when working remotely.

Quick Start

Run talosctl with the provided talosconfig to manage the cluster from a remote workstation.

Frequently Asked Questions about anton-remote-access

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I access a Kubernetes cluster remotely using Tailscale?

Remote Kubernetes cluster access via Tailscale requires using MagicDNS to route talosctl and kubectl traffic from an off-LAN workstation to the cluster nodes securely.

How do I use talosctl to manage a Talos cluster off-LAN?

To manage a Talos cluster off-LAN, run talosctl with a valid talosconfig file that targets cluster nodes through the Tailscale Tailnet using MagicDNS resolution.

Do I need Tailscale MagicDNS to run kubectl against a remote cluster?

Tailscale MagicDNS is needed to resolve cluster node addresses for kubectl when operating off-LAN, ensuring the kubeconfig context can successfully route traffic to the correct endpoints.

What is the best way to manage kubectl contexts when working remotely?

Managing kubectl contexts remotely involves enforcing safe handling of your kubeconfig and maintaining Tailnet hygiene to prevent exposing real tailnet names during context switching.

Why is my talosctl connection to cluster nodes not working over Tailnet?

Talosctl connection issues over Tailnet often stem from incorrect talosconfig paths, unresolved MagicDNS entries, or poor Tailnet hygiene, which the troubleshooting steps in the Skill address.