Backup/restore of master

[andyjeffries]

Considering how K3s is really currently positioned as having a single master, we thought it would be nice if there was a way of backing up and restoring the K3s master content (so we could wipe the master's virtual machine, rebuild it, re-install with a backup file given to use it during installation).

Describe the solution you'd like
An option to k3s to perform a backup, an ENV option during the installer to use an existing backup.

Describe alternatives you've considered
A simple bash script that copies the related files, but it wouldn't feel as nice.

Additional context
We're happy to have a whack at building this and submitting PRs, just wanted to check first if there was any interest in it?

[dewet22]

HA just got its first love with v0.7.0 and presumably will keep on maturing, so not sure how useful this is going forward?

That said, k3s master state is all under /var/lib/rancher/k3s/server, and my current strategy is snapshotting that regularly for the time being. In fairness I haven't tested the restore part yet :D

[dheeraj29]

Why not try

https://github.com/heptio/velero

[andyjeffries]

I'm thinking more along the lines of as (below 0.7.0) k3s was a generally single master solution and we're offering a public managed K3s service, having the ability to backup/restore the master would be great. With it moving towards a full HA system, this may be less necessary. But I wasn't thinking of backing up and restoring the cluster contents themselves.

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.

[unixfox]

Bump still important feature.

[maxirus]

I see the callout in the Rancher Backup/Restore Docs:

Currently, backups of SQLite are not supported. Instead, make a copy of /var/lib/rancher/k3s/server and then delete K3s.

But it doesn't go into much more detail than that. Will following steps work?

1. Make note of K3s Server version
2. Stop master/server
3. zip folder /var/lib/rancher/k3s/server
4. bring new host up
5. Restore zip file
6. Install same version of k3s-server

[stale]

This repository uses a bot to automatically label issues which have not had any activity (commit/comment/label) for 180 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the bot can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the bot will automatically close the issue in 14 days. Thank you for your contributions.