Skip to content

fix(talos): rotate the Talos API CA and machine token - #4946

Merged
dapperdivers merged 2 commits into
mainfrom
feat/talos-ca-token-rotation
Nov 21, 2026
Merged

dapperdivers merged 2 commits into
mainfrom
feat/talos-ca-token-rotation

Conversation

@dapperdivers

Copy link
Copy Markdown
Owner

The Talos machine CA private key and the machine token were printed into a Claude Code session transcript on 2026-11-21. zsh MULTIOS copied render.sh stdout into a pipe even with >/dev/null. Both are rotated and live.

Commits

  1. Talos API CA: talosctl rotate-ca --talos=true --kubernetes=false across all 11 nodes (accept new, switch issuing, remove old, connectivity checked at each step, no reboots). talsecret.sops.yaml certs.os updated via sops set --value-stdin. The old talosconfig is rejected ("certificate signed by unknown authority"). Talos re-issued the talos.dev ServiceAccount secrets (tuppr, ARC runner) under the new CA; tuppr was restarted and has no TLS errors.
    Also: render.sh now exits when stdout is a terminal.
  2. Machine token: new trustdinfo.token, applied to control planes then workers, no reboots. 0 trustd rejections.

Verified

  • Talos API reachable on 11/11 nodes; 11/11 nodes Ready.
  • task talos:diff-cluster: 11/11 No changes., so the repo matches what is running.
  • A talosconfig minted from the bundle authenticates to the cluster.
  • Encrypted pre-rotation backups are in .private/backups/2026-11-21-pre-talos-ca-rotation/ and Infisical /Infrastructure/Talos/Backups (TALOS_BACKUP_20261121_PRECA_*).

Any talosconfig on other machines must be replaced with the new one.

…terminal

The Talos machine CA private key and the machine token were printed into a
session transcript (render.sh output piped through zsh, whose MULTIOS copied
stdout to the pipe despite >/dev/null). This rotates the CA; the machine
token follows in the next commit.

- `talosctl rotate-ca --talos=true --kubernetes=false` on all 11 nodes:
  new CA accepted, made issuing, old CA removed, with connectivity checked
  at each step; no reboots. The old talosconfig is now rejected
  ("certificate signed by unknown authority").
- talsecret.sops.yaml certs.os.{crt,key} set to the new CA (sops set
  --value-stdin, copied from the live control-plane config). A talosconfig
  minted from the bundle authenticates; diff-cluster shows 11/11 nodes
  "No changes."
- render.sh exits when stdout is a terminal, since its output holds CA keys
  and tokens.
- Talos re-issued the talos.dev ServiceAccount secrets (tuppr, ARC runner)
  under the new CA; tuppr restarted.
The machine token (trustdinfo.token) was exposed alongside the Talos CA key.
New token generated with talosctl gen secrets and written with sops set
--value-stdin; nothing else in the bundle changed. Applied to the control
planes, then the workers (no reboots). Talos API reachable on 11/11 nodes,
no trustd rejections, diff-cluster 11/11 "No changes."
@dapperdivers
dapperdivers merged commit 3448863 into main Nov 21, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant