eblume/blumeops
1
1
Fork 0
Code Issues Pull requests Projects Releases 83 Packages Wiki Activity Actions
blumeops/docs/reference/kubernetes/tailscale-operator.md
Erich Blume c130f72204 Update all docs titles to human-readable and delete test cards 
Titles now use proper casing (e.g. "Borgmatic" instead of "borgmatic",
"AI Assistance Guide" instead of "ai-assistance-guide") and match file
stems so wiki-links work without alternate anchor text. Also removes
the title-test-alpha/beta cards and their reference index entry.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-07 21:40:22 -08:00

1 KiB
Raw Blame History

title tags
Tailscale Operator
kubernetes
tailscale

Tailscale Kubernetes Operator

The Tailscale operator enables Kubernetes services to be exposed directly on the Tailscale network via Ingress resources.

Quick Reference

Property Value
Namespace tailscale
Helm Chart tailscale/tailscale-operator
ArgoCD App tailscale-operator

How It Works

When you create an Ingress with ingressClassName: tailscale:

  1. Operator provisions a Tailscale node for the service
  2. Service becomes accessible at <hostname>.tail8d86e.ts.net
  3. TLS is handled automatically via Tailscale

Limitations

Services exposed via Tailscale Ingress are not accessible from:

  • Other Kubernetes pods (they're not Tailscale clients)
  • Docker containers on indri

For pod-to-service communication, use routing (*.ops.eblu.me) instead.

Related