https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
m
It's everything that is needed to restore Rancher itself, but not the entire cluster
Just run a backup and download it from object storage, it's a simple tarball, so you can easily see what's included
b
Ah. Ok. And what about backing up the cluster? Like all the CRDs and manifests and especially the secrets?
I guess, if you are following gitops practices, that's the back up, in a sense, for the cluster's config.
Hmm.... I guess secrets are the only thing that are concerning me really. Any suggestions on how to handle them best?
m
You're looking for etcd backup.
However, snapshots are stored locally, so this is only helpful in case you accidentally delete somethig, not if all control plane nodes are lost. For disaster recovery, you would have to set up S3 storage for etcd snapshots, see documentation.
r
Hi, You have 2 types of backup in rancher: backup etcd and backup/restore operator. The first backup etcd is enabled by default when you install rke2 or k3s and backup the cluster configuration stored in your etcd database. The second backup/restore is an operator installed in your cluster which allowed to backup the crd, and all kubernetes objets(pod, deployment ...). NB: if you use fleet, this operator cannot backup the fleet secret. You must recreate manually your fleet secret after the restore.
q
When I import clusters into Rancher, does etcd backup contain those clusters to be restored at a later time?
16 Views
Open in Slack
PreviousNext
Powered by