Add or replace Talos nodes in the Anton Kubernetes cluster via talosctl.
npx skills add https://github.com/wcygan/anton --skill add-or-replace-node
Please help me install this Agent Skill. Skill: add-or-replace-node Source: https://github.com/wcygan/anton/tree/main/.claude/skills/add-or-replace-node Command: npx skills add https://github.com/wcygan/anton --skill add-or-replace-node
This skill enables safe expansion, replacement, or reconfiguration of nodes in the Anton Talos-based Kubernetes cluster, including scaffolding, patch generation, and applying changes via talosctl.
Provision a new node, update the Talos config, render the machine configs, and push them with talosctl.
High-intent search queries and answers about installing and using this skill.
To replace a failed Talos node safely, you generate per-node patches, render the updated machine configs, and apply them via talosctl. This workflow preserves etcd quorum and maintains cluster health during the hardware replacement.
Adding a new Talos node involves provisioning the hardware, updating the Talos configuration, generating per-node patches, rendering machine configs, and applying the changes with talosctl to ensure proper onboarding and post-join verification.
Yes, you can rename or remove a Talos node by performing cleanup and config adjustments. The process guides you through applying changes via talosctl while preserving the overall health and etcd quorum of the cluster.
The safest way to apply machine config patches is through an automated workflow that renders per-node configurations and pushes them using talosctl. This ensures cluster health and maintains etcd quorum during node expansion or replacement.
After adding a Talos node, post-join verification involves checking cluster health and ensuring the new node has successfully joined without disrupting etcd quorum. The workflow includes built-in guidance for these required health checks.
wcyganAlign Longhorn disk configurations with Talos per-node patches via kubectl.
wcyganPerform rolling Talos OS or Kubernetes upgrades with etcd quorum checks.
cnoe-ioQuery EKS clusters via kubectl and report pod, node, and resource health.
superagiPlan and execute multi-channel outreach sequences with granular step control.
