-
Notifications
You must be signed in to change notification settings - Fork 101
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
Multi-Node ETCD Backup & Restore #33
Comments
Yes. We can extend it. Although this breaks up the initial assumption of having single node cluster we had considered while designing it. So, there are some complications involved. So, from gardener ring's perspective we will have three statefulSets running in three different clusters. Probably we will have to bring in logic of leader election there for backup sidecar so that only one backup sidecar can modify object store. Restoration would be the tricky part, we will have to carefully handle different cases like network partitioning, valid PV but not completely synced. But i think its feasible. Overall in my opinion it is extensible, but only condition is, to have all etcd names and url available before starting cluster. and tls certificate created/configured appropriately. Its quite a work, worth giving a shot, from gardener ring's perspective. |
Thank you for the feedback! |
Moved to gardener/etcd-druid#107 |
In context of the Gardener ring, @rfranzke and @mandelsoft raise the question whether the current solution can be retrofitted for backup & restore in the multi-node Gardener ring.
The text was updated successfully, but these errors were encountered: