Skip to content

Longhorn Storage

Continuous persistent storage for Kubernetes workloads is provided by Longhorn.

Namespace: longhorn-system
Chart: longhorn/longhorn

1. Overview

Persistent storage is provided on a single K3s node. Longhorn volumes are healthy and provide snapshots/backups, but the current replication factor is one; this is not storage high availability.

2. Architecture and Replication

  • Replication Factor: 1
  • Backup Target: Configured Longhorn backup target.
  • Frontend: Web UI accessible via internal cluster ingress.
  • Node: k3s-master

3. Implementation Steps

  1. System Preparation: Ensure open-iscsi and nfs-common are installed on the active K3s node.
  2. Deployment: Installed via ArgoCD using the official Helm chart.
  3. StorageClass: Set as the cluster default StorageClass for automatic provisioning.

4. Maintenance and Backup

  1. Snapshot Schedule: Automated backup jobs protect active application volumes.
  2. Node Maintenance: Schedule maintenance carefully because all Longhorn volumes are attached to the single node.
  3. Health Monitoring: Volume health is monitored through the Longhorn UI and Prometheus alerts.