longhorn-node-ops

Align Longhorn disk configurations with Talos per-node patches via kubectl.

3|Updated May 13, 2025
One-click install
npx skills add https://github.com/wcygan/anton --skill longhorn-node-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: longhorn-node-ops
Source: https://github.com/wcygan/anton/tree/main/.claude/skills/longhorn-node-ops
Command: npx skills add https://github.com/wcygan/anton --skill longhorn-node-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables safe management of Longhorn disks on Talos nodes, including adding or removing disks, evicting replicas before maintenance, and integrating replaced nodes into the topology.

Core Features & Use Cases

  • Coordinate Longhorn disk topology with the Talos per-node patch to align node state with Longhorn.
  • Evict replicas before maintenance and fix disk-routing mismatches to prevent data loss during reconfigurations.
  • Integrate a replaced node into Longhorn topology and recover from disk matching drift observed after node changes.

Quick Start

Run longhorn-node-ops to align Longhorn disks with the Talos per-node patch before rebooting a node.

Frequently Asked Questions about longhorn-node-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align Longhorn disk configurations with Talos node patches?

To align Longhorn disk configurations with Talos node patches, validate per-node disk definitions via Talos annotations and apply Longhorn disk updates through kubectl patches to prevent topology mismatch during maintenance.

How do I evict Longhorn replicas before node maintenance?

Evicting Longhorn replicas before node maintenance requires coordinating disk topology with the Talos per-node patch to safely reroute data and prevent loss during reboots or disk replacements.

Why does Longhorn disk topology drift after replacing a Talos node?

Longhorn disk topology drift occurs after replacing a Talos node when per-node disk definitions mismatch the Longhorn configuration, requiring validation via Talos annotations and kubectl patches to repair routing.

Can I use kubectl to integrate a replaced Talos node into Longhorn topology?

Yes, you can integrate a replaced Talos node into Longhorn topology by applying kubectl patches that update Longhorn disk definitions based on validated Talos per-node annotations.

What is the best way to fix disk-routing mismatches in Longhorn on Talos?

Fixing disk-routing mismatches in Longhorn on Talos involves validating per-node disk definitions through Talos annotations and applying kubectl patches to synchronize Longhorn disk state with Talos configuration.

Do I need to validate Talos annotations before patching Longhorn disks?

Yes, validating Talos per-node annotations for disk definitions is required before applying kubectl patches to Longhorn, ensuring disk updates align with the actual Talos node configuration and preventing data loss.