Repository navigation
fix(talos): rotate the Talos API CA and machine token - #4946
Merged
Merged
Conversation
…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."
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.shstdout into a pipe even with>/dev/null. Both are rotated and live.Commits
talosctl rotate-ca --talos=true --kubernetes=falseacross all 11 nodes (accept new, switch issuing, remove old, connectivity checked at each step, no reboots).talsecret.sops.yamlcerts.osupdated viasops 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.shnow exits when stdout is a terminal.trustdinfo.token, applied to control planes then workers, no reboots. 0 trustd rejections.Verified
task talos:diff-cluster: 11/11No changes., so the repo matches what is running..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.