(Longhorn/K3s) Failed cluster, made new cluster, are PVs salvageable?

This page summarizes the projects mentioned and recommended in the original post on /r/kubernetes

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • k3s-ansible

    The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat. (by techno-tim)

    I recently broke my cluster somehow (see this thread) so I decided to start fresh because I can't get K3s up and running again. I now have 5 nodes (3 master, 2 worker) with etcd configured using the K3s-ansible guide found here. Is it possible to recover the PVs from my failed cluster? I still have SSH access to each of the machines that participated in the cluster. It would save me a lot of rebuilding time if I could extract them (even from an older backup, if Longhorn stores them in an accessible format) and apply to the new cluster.

  • velero

    Backup and migrate Kubernetes applications and their persistent volumes

    You can also leverage https://velero.io/ to backup both cluster state and pvc state to s3

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts