You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When we deploy nodes, we generate a unique suffix for its name. For upgrades and changes we rebuild the nodes which in turn generates a new suffix on its name. The issue we are running into is the etcd backup process saves the files using the node name and also uses that for the pruning process. Since our node names often change, all old backups are not deleted automatically.
Describe the solution you'd like
Allow us to provide a backup prefix/name override that way even if the node name changes, the backup names are kept the same. Basically we would set this to the node name without the suffix.
Describe alternatives you've considered
Build some custom process to delete the backups outside rke2.
Additional context
none
The text was updated successfully, but these errors were encountered:
mitchellmaler
changed the title
ETCD Backup File Name/Prefix Override
ETCD S3 Backup File Name/Prefix Override
Nov 30, 2022
Is your feature request related to a problem? Please describe.
When we deploy nodes, we generate a unique suffix for its name. For upgrades and changes we rebuild the nodes which in turn generates a new suffix on its name. The issue we are running into is the etcd backup process saves the files using the node name and also uses that for the pruning process. Since our node names often change, all old backups are not deleted automatically.
Describe the solution you'd like
Allow us to provide a backup prefix/name override that way even if the node name changes, the backup names are kept the same. Basically we would set this to the node name without the suffix.
Describe alternatives you've considered
Build some custom process to delete the backups outside rke2.
Additional context
none
The text was updated successfully, but these errors were encountered: