-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ETCD S3 Backup File Name/Prefix Override #3610
Comments
mitchellmaler
changed the title
ETCD Backup File Name/Prefix Override
ETCD S3 Backup File Name/Prefix Override
Nov 30, 2022
Updated name to include s3. This is around the automated s3 backup process in rke2. |
Lets track this in #3714 - I believe the underlying issue is the same. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: