k3s-gitops

Manage a 3-node k3s cluster with GitOps, ArgoCD, and Longhorn.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/unixfg/skills --skill k3s-gitops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k3s-gitops
Source: https://github.com/unixfg/skills/tree/main/k3s-gitops
Command: npx skills add https://github.com/unixfg/skills --skill k3s-gitops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive solution for managing a 3-node k3s Kubernetes cluster using GitOps, addressing common operational tasks and troubleshooting scenarios.

Core Features & Use Cases

  • Cluster Maintenance: Perform node operations, manage storage, and troubleshoot ArgoCD sync issues.
  • Troubleshooting: Diagnose and resolve Longhorn storage problems, including faulted volumes.
  • GitOps Workflow: Facilitates cluster updates and management through a Git repository.
  • Use Case: When a Longhorn volume becomes faulted, this Skill guides you through the steps to salvage or recreate it, ensuring data integrity and cluster stability.

Quick Start

Use the k3s-gitops skill to check the health of all Longhorn nodes and volumes before performing maintenance.

Frequently Asked Questions about k3s-gitops

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

FAQPage Schema
How do I recover a faulted Longhorn volume in a k3s cluster?

To recover a faulted Longhorn volume in a k3s cluster, you must follow specific troubleshooting steps to salvage or recreate it. This ensures data integrity and restores cluster stability during maintenance operations.

What is the best way to manage k3s cluster maintenance using GitOps?

Managing k3s cluster maintenance via GitOps involves using ArgoCD to synchronize cluster states and performing node operations through a Git repository. This includes pre-flight checks and drain procedures for safe updates.

How do I troubleshoot ArgoCD synchronization issues in Kubernetes?

Troubleshooting ArgoCD synchronization issues in Kubernetes requires diagnosing configuration mismatches and webhook configurations. You resolve these by aligning the live cluster state with your Git repository declarations.

Do I need to check Longhorn volumes before draining a k3s node?

Yes, you must check the health of all Longhorn nodes and volumes before draining a k3s node. Performing pre-flight checks prevents data loss and ensures workload stability during node maintenance.

Why does my ArgoCD webhook configuration fail on a 3-node k3s cluster?

ArgoCD webhook configuration on a 3-node k3s cluster can fail due to incorrect endpoint routing or Git repository payload formatting. Troubleshooting involves validating webhook delivery and cluster ingress settings.