Skip to content
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

[etcdsnapshot&restore] Create a single automatic snapshot per cluster #764

Open
Danil-Grigorev opened this issue Oct 1, 2024 · 0 comments
Assignees
Labels
area/etcdsnapshot-restore Categorizes issue or PR as related to Turtles ETCD Snapshot & Restore feature kind/feature

Comments

@Danil-Grigorev
Copy link
Contributor

Danil-Grigorev commented Oct 1, 2024

To reduce number of created snapshots per cluster, we can encapsulate multiple automatic snapshots for a cluster in a single resource within the resource status, instead of creating a separate one per each automatic snapshot.

This should address scalability concerns and provide a better UX working with automatic RKE2 snapshots.

Context from proposal:

Just an idea here: potentially this number can be decreased from N*M to just N where N is the number of clusters and M is the ~number of preserved snapshot per each cluster, if the automatic snapshot will be treated as a “full cluster” state. Instead of creating a resource per each snapshot resource, there will be one snapshot resource synced to the management cluster. Automation will take care of updating name of the node and file/S3 reference, where the snapshot has taken place inside this single resource, and potentially specifying alternative up-to-date snapshots in a status, which can be used as a source for restore.

@furkatgofurov7 furkatgofurov7 added the area/etcdsnapshot-restore Categorizes issue or PR as related to Turtles ETCD Snapshot & Restore feature label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/etcdsnapshot-restore Categorizes issue or PR as related to Turtles ETCD Snapshot & Restore feature kind/feature
Development

No branches or pull requests

3 participants