Private Networking on Hetzner Cloud with Tailscale

Onat Yigit Mercan· May 17, 2026 · 11:17 AM UTC ·4 min read · 0 reactions · 0 comments · 36 views

#networking #kubernetes #terraform #tailscale #cloud-infrastructure

TL;DR · WeSearch summary

The article describes setting up a private network on Hetzner Cloud using Tailscale to create a VPC-style environment for a self-hosted Kubernetes cluster. The architecture ensures cluster nodes have no public IPs, with all egress routed through a single NAT gateway. Access to the cluster is secured via Tailscale, allowing private-only connectivity for internal tools while keeping public applications accessible over the internet.

Key facts

▪The Kubernetes cluster is deployed in a private network (10.0.0.0/16) with no public IPs except for a single NAT gateway.
▪Tailscale is used to enable secure access to the private network through subnet routing and device authentication.
▪Public applications are exposed via a public load balancer, while internal services remain accessible only within the Tailnet.
▪The NAT gateway performs MASQUERADE NAT and advertises the private subnet to the Tailnet using Tailscale's routing features.
▪Terraform manages the infrastructure, including network configuration, firewall rules, and Tailscale ACLs for access control.

About this source

Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.

All Hacker News (Newest) coverage →

Original article

Onat Mercan’s Blog · Onat Yigit Mercan

Read full at Onat Mercan’s Blog →

Story provenance

Source · retrieval · rights · ranking — open for full record

inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisher	Onat Mercan’s Blog
Canonical URL	https://onatm.dev/2026/01/28/private-networking-on-hetzner-cloud-with-tailscale/
Publication time	Sun, 17 May 2026 11:17:41 +0000
Retrieval time	2026-05-17T11:22:13.108Z
Last seen	2026-05-17T11:22:13.108Z
Headline source	Publisher (no WeSearch rewrite)
Excerpt source	publisher body
Excerpt method	First ~120 words (~800 chars) of extracted publisher body, fair-use limited.
Summary	WeSearch · cerebras-chat (WeSearch summarizer)
Summary source text	contentText
Citation coverage	Summary is a WeSearch-generated derivative; primary citation is the original publisher URL.
Cluster	WyUz-j3Us6wT
Cluster logic	Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reason	Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visit	Yes — open original
Substitutes article?	No — link-out required for full text

Rights status (four layers)

Publisher-declared

No publisher-confirmed rights record for this source yet.

Machine-readable

No source-specific machine-readable restriction detected beyond the public feed.

WeSearch interpretation

WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.

Unknown

Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing	May the item be indexed (stored, ranked, made findable)?	Allowed
Snippet	May a short excerpt of the publisher's text be shown?	Allowed
AI summary	May WeSearch generate its own short summary of the article?	Limited
Retrieval / RAG	May the content be exposed for third-party retrieval-augmented generation?	Not asserted
Model training	May the content be used to train AI models?	Not asserted
Commercial reuse	May the content be reused commercially?	Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Open original publisher → Source rights JSON → Machine-readable provenance → Rights framework → WESEARCH-STORY-PROVENANCE-V1

Opening excerpt (first ~120 words) tap to expand

Private Networking on Hetzner Cloud with Tailscale January 28, 2026 • 5 min read infrastructure kubernetes networking terraform tailscale hetzner This is a follow up to Why I Built My Own Kubernetes Cluster The cluster post was about why I built my own Kubernetes cluster. This one is about the private network that makes the rest possible. I wanted the cluster to live in a VPC-style network with zero public node IPs, reachable only from my own internal network. Tailscale is the bridge here. I keep Raspberry Pi Zero exit nodes across Europe with friends for VPN use, so I already use Tailscale a lot. That’s why it was the obvious choice for private access. What I Wanted from the Network I wanted three things: Private-only cluster nodes: no public IPs anywhere except one gateway.

…

Excerpt limited to ~120 words for fair-use compliance. The full article is at Onat Mercan’s Blog.

Anonymous · no account needed

Discussion

0 comments