T

jeffryandClaude Opus 5 804ed08b84 take the node address out of a public example

An internal IP in a public document is not routable and still names the subnet,
and the example does not need a literal — the check is that a hostname with no
listener returns 404, and any node address demonstrates it.

Caught by grepping the fresh public history for anything version- or
address-shaped, which is a thing worth doing once per repository that changes
visibility.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-07 15:20:28 -04:00

.loom

take the node address out of a public example

2026-09-07 15:20:28 -04:00

README.md

the published surface, on a fresh root

2026-09-07 15:19:14 -04:00

README.md

homelab-cluster

What a three-node k3s cluster on a home LAN offers, for somebody deciding whether to put something on it.

Six documents in .loom/published/ — and one thing we need and cannot find, in .loom/gaps/.

Start with .loom/README.md.

What is not here

How the cluster is built. Manifests, Helm values, the rebuild guide, the inventory of what is running and at which version. That is jeffry/homelab-impl and it is private, because a version inventory is a target list for anybody matching published vulnerabilities.

Nothing on this side links to that side. A public page naming a private thing as its answer costs the reader a request and their confidence in the rest of the page.

Each document here ends with how to check it is still true. Nothing serves the truth about a running cluster, so the only mechanism is somebody looking.