Perform rolling Talos OS or Kubernetes upgrades with etcd quorum checks.
npx skills add https://github.com/wcygan/anton --skill upgrade-talos-or-k8s
Please help me install this Agent Skill. Skill: upgrade-talos-or-k8s Source: https://github.com/wcygan/anton/tree/main/.claude/skills/upgrade-talos-or-k8s Command: npx skills add https://github.com/wcygan/anton --skill upgrade-talos-or-k8s
Rolling upgrades for Anton's Talos OS or Kubernetes are performed patch-by-patch with etcd quorum checks.
Bump the desired version pin in talos/talenv.yaml, re-render machine configs, and run the appropriate rolling upgrade workflow.
High-intent search queries and answers about installing and using this skill.
Safe rolling upgrades require upgrading control planes before workers, node-by-node, with health gates between nodes. You must maintain etcd quorum checks throughout the process and use a clear rollback path if failures occur.
Etcd quorum validation during Kubernetes control plane upgrades works by enforcing per-node health gates between sequential patch updates. This strict sequencing ensures your cluster maintains a healthy quorum before proceeding to the next control plane node.
To bump the Talos OS version, update the talosVersion pin in talos/talenv.yaml, re-render the machine configs, and execute the rolling upgrade workflow to apply the patch-by-patch updates across your nodes.
Yes, the workflow covers both OS and Kubernetes version bumps. You update the respective version pins in talos/talenv.yaml, re-render configurations, and apply the upgrades sequentially across your nodes while maintaining health gates.
Required pre-flight checks for a Talos cluster upgrade include taking etcd snapshots, validating cluster health, and verifying version pin management in talenv.yaml. These steps ensure consistency and provide a rollback path for failed upgrades.
To handle a failed Kubernetes node upgrade in Talos, utilize the predefined rollback path. The workflow's strict sequencing and per-node health gates isolate failures, allowing you to safely revert the failed node without losing etcd quorum.
sigridjinethAutomates Kubernetes cluster lifecycle via managed Airflow deployments.
openshiftDiagnose NotReady or SchedulingDisabled OpenShift nodes and prescribe recovery actions.
AgoricAutomate patch management for local dependency patches across patching tools.
ChatAndBuildDesign CI/CD deployment pipelines with promotion stages, quality gates, and rollback paths.
