Ephemeral Castle Topology Drift

Scope

This page records a small but important drift between older prose docs and the current code-backed cluster topology.

Finding

  • clusters/tazlab-k8s/BOOTSTRAP.md still describes an older 1 control-plane + 2 workers shape.
  • clusters/tazlab-k8s/live/env.hcl currently encodes 1 control-plane node and 1 worker node.
  • clusters/tazlab-k8s/modules/proxmox-talos/main.tf consumes those maps directly, so the Terragrunt/Terraform path follows the 1+1 topology.

Current Truth

The current code truth is 1 control plane and 1 worker. That is the topology future documentation should treat as authoritative unless env.hcl changes.

Why It Matters

Topological drift is easy to miss when bootstrap docs are written as a narrative and the live topology is later reduced. If future work assumes the older 2-worker shape, the docs will mislead operators about VM IDs, storage layout, and bootstrap timing.

Source Basis

  • clusters/tazlab-k8s/BOOTSTRAP.md
  • clusters/tazlab-k8s/live/env.hcl
  • clusters/tazlab-k8s/modules/proxmox-talos/main.tf