Menu
Use when removing, replacing, or decommissioning a Talos node — covers the correct talosctl reset workflow
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit CloudNativePG (CNPG) clusters for backup health, S3 storage bloat, and disk-space risk — schedule misconfiguration, WAL/archive_timeout churn, orphaned backups, compression, and PVC resize status. Use when investigating CNPG backup storage growth, a "storage near empty" alert on the backup target (e.g. QNAP), a crash-looping/"Not enough disk space" CNPG cluster, or doing a periodic CNPG health check.
Push an updated Coder workspace Terraform template and redeploy running workspaces onto it. Use when workspace-template/main.tf changes (resources, volumes, etc.) need to reach live Coder workspaces.
Diagnose and fix ONLYOFFICE Document Server showing "An error has occurred while opening the file" with no failed requests visible in the browser. Root cause is usually an orphaned task_result row in the docserver's Postgres DB, left over from a conversion interrupted by a pod crash/OOM/restart.
Task commands, bootstrap sequence, CI/CD, branch/PR workflow, linting, and devcontainer setup for the home-ops repository.
Use when auditing disk health, filesystem usage, or I/O on cluster nodes — especially when filesystem queries return incomplete results or a node's second drive is missing from metrics.
Reference for cluster infrastructure components, Talos configuration, network topology, and auto-managed files. Use when querying component roles, versions, IPs, or understanding what files must not be manually edited.
| name | talos-node-removal |
| description | Use when removing, replacing, or decommissioning a Talos node — covers the correct talosctl reset workflow |
| user-invocable | false |
| origin | auto-extracted |
Extracted: 2026-06-12 Context: Removing a control plane or worker node (hardware replacement, decommission, OS reinstall)
Manual node removal requires 4+ steps in the correct order (cordon → drain → etcd remove-member → kubectl delete → shutdown). Wrong order risks etcd split-brain or the node failing to rejoin after reinstall.
talosctl reset handles everything automatically — cordons, drains, leaves etcd, erases disk, powers off:
# Step 1: Reset the node (handles cordon/drain/etcd-leave/erase/shutdown)
talosctl -n <node-ip> reset
# Step 2: Remove the Kubernetes node object (reset does NOT do this)
kubectl delete node <node-name>
The machine is powered off after reset. To reinstall (e.g. after hardware swap):
# Verify cluster version before applying
talosctl version -n <other-node-ip>
# Boot from Talos ISO, apply existing machine config
talosctl apply-config --insecure -n <node-ip> \
-f provision/talos/clusterconfig/<node>.yaml
Talos installs onto the new disk and rejoins etcd automatically. No uncordon needed — nodes join uncordoned.
etcd requires 2/3 quorum — never reset two control plane nodes simultaneously.
Official docs: https://docs.siderolabs.com/talos/v1.13/deploy-and-manage-workloads/scaling-down