Frank, the Talos Cluster: Overview & Roadmap

The Frank, the Talos Cluster series is a walkthrough of building an AI-hybrid Kubernetes homelab from scratch, one layer per post. This post is not part of that walkthrough. It is the index to it: the roadmap, the capability map, the hardware, and a set of commands for checking whether any of it is still true.

Roadmap

Technology → Capability Map

Cluster State

Four zones, lettered A to D. Zone A is management and has no row here on purpose: it lives outside the cluster, so it has no node to appear as. The other three are the cluster.

Verify this page against a live cluster

Everything in the Technology → Capability Map arrives as an ArgoCD Application, so the table is checkable rather than a claim you have to take on trust. The kubectl lines below want a kubeconfig for a cluster; the grep lines want a clone of derio-net/frank and run from its root.

Every number below was captured on 2026-07-29 and will have moved since. The command is the durable part; the digits are a sample so you can tell whether you typed it right. Start with the count:

$ kubectl -n argocd get applications --no-headers | wc -l
      69

Sixty-eight of those are templated by the App-of-Apps. The sixty-ninth is root itself, applied by hand once at bootstrap, because at that moment nothing exists yet to apply it:

$ grep -l 'kind: Application' apps/root/templates/*.yaml | wc -l
      68

That arithmetic is the whole GitOps claim in one line. When the two numbers stop agreeing, something on the cluster was made outside git.

Existing and converged are different questions, so ask the second one separately:

$ kubectl -n argocd get applications \
    -o jsonpath='{range .items[*]}{.status.sync.status}{" "}{.status.health.status}{"\n"}{end}' \
  | sort | uniq -c | sort -rn
  62 Synced Healthy
   5 OutOfSync Healthy
   1 Synced Suspended
   1 OutOfSync Missing

Sixty-two green out of sixty-nine, on an ordinary afternoon. Suspended is a canary parked at a manual promotion gate — Argo Rollouts doing its job, not a fault. OutOfSync is live state disagreeing with git. Neither is an emergency, and a cluster reporting all green all the time is usually one nobody is asking hard questions of.

The roadmap at the top is numbered by published post. The layer codes that plan filenames and commit messages use are a separate registry:

$ grep -c '^  - code:' docs/layers.yaml
22

Twenty-one numbered capability layers, plus repo for meta-work that is not a cluster capability at all. The two sequences match through Layer 17 and diverge after it, because layers stopped shipping in the order they were planned. If you are looking for the post that covers a layer, follow the roadmap; if you are looking for the plan that built it, follow the code.

Missteps

Three forks where the obvious choice was the wrong one.