Through the Backup Destinations settings you can enable and configure the new etcd backups for each Seed.
Etcd Backup Settings
Setting a Bucket and Endpoint for a Seed turns on the automatic etcd Backups and Restore feature, for that Seed only. For now, we only support S3 compatible endpoints.
It is possible to set multiple destinations per Seed, so that for example some backups can go into the local minio, and some to an S3 bucket, depending on the importance.
For users already using the backups introduced in 2.18, when only one backup bucket and endpoint was available, they need to migrate to using destinations from 2.20 as backups without destination are not supported anymore.
To add a new backup destination, just click on the Add Destination button on the right.
When a destination is added, credentials also need to be added for the bucket. To do that, click on the Edit Credentials
button and set the credentials. When credentials are properly set, the green checkmark appears and the destination can be used.
To edit, just click on the Edit Destination pen icon on the right
Credentials
When a destination is added, credentials also need to be added for the bucket. To do that, click on the Edit Credentials
button and set the credentials. When credentials are properly set, the green checkmark appears and the destination can be used.
For security reasons, the API/UI does not offer a way to get the current credentials.
To see how to make backups and restore your cluster, check the Etcd Backup and Restore Tutorial.
Default Backups
Since 2.20, default destinations are required if the automatic etcd backups are configured. A default EtcdBackupConfig is created for all the user clusters in the Seed. It has to be a destination that is present in the backup destination list for that Seed.
Example Seed with default destination:
...
etcdBackupRestore:
destinations:
s3:
bucketName: kkpbackuptest
credentials:
name: backup-s3
namespace: kube-system
endpoint: s3.amazonaws.com
defaultDestination: s3
...
Default EtcdBackupConfig that is created:
...
spec:
keep: 20
name: default-backups
schedule: '@every 20m'
destination: s3
...
