Our great sponsors
-
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.
-
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.
Related posts
- What is the proper, kubernetes native way of working with multiple clusters for DR, HA?
- How can I route some pods through a Wireguard pod?
- MetalLB Routing on Hetzner Bare Metal
- Is there a way to clone an existing Azure Kubernetes Cluster?
- What are the best practices for backing up k8S related ressources in RKE2 clusters running on VSphere ?