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

Multi-Node ETCD Backup & Restore #33

Closed
vlerenc opened this issue Jun 21, 2018 · 3 comments
Closed

Multi-Node ETCD Backup & Restore #33

vlerenc opened this issue Jun 21, 2018 · 3 comments
Labels
area/backup Backup related area/disaster-recovery Disaster recovery related component/etcd-backup-restore ETCD Backup & Restore kind/enhancement Enhancement, improvement, extension topology/garden Affects Garden clusters topology/seed Affects Seed clusters
Milestone

Comments

@vlerenc
Copy link
Member

vlerenc commented Jun 21, 2018

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.

@vlerenc vlerenc added kind/question Question (asking for help, advice, or technical detail) lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) topology/garden Affects Garden clusters component/etcd-backup-restore ETCD Backup & Restore and removed lifecycle/icebox Temporarily on hold (will not age; may have dependencies, lack priority, miss feedback, etc.) labels Jun 21, 2018
@swapnilgm
Copy link
Contributor

swapnilgm commented Jun 22, 2018

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.

@vlerenc
Copy link
Member Author

vlerenc commented Jun 22, 2018

Thank you for the feedback!

@vlerenc vlerenc added area/disaster-recovery Disaster recovery related kind/enhancement Enhancement, improvement, extension area/backup Backup related platform/all and removed kind/question Question (asking for help, advice, or technical detail) labels Jun 27, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 27, 2018
@swapnilgm swapnilgm added this to the 0.5.0 milestone Oct 24, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Dec 24, 2018
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Feb 23, 2019
@vlerenc vlerenc added topology/seed Affects Seed clusters and removed platform/all labels Apr 18, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 18, 2019
@gardener-robot-ci-1 gardener-robot-ci-1 added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Aug 18, 2019
@gardener-robot-ci-3 gardener-robot-ci-3 added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Oct 18, 2019
@ghost ghost removed the lifecycle/stale Nobody worked on this for 6 months (will further age) label Oct 18, 2019
@swapnilgm swapnilgm removed this from the 0.5.0 milestone Nov 22, 2019
@swapnilgm swapnilgm added this to the 0.9.0 milestone Nov 22, 2019
@swapnilgm swapnilgm pinned this issue Nov 22, 2019
@ghost ghost added lifecycle/stale Nobody worked on this for 6 months (will further age) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jan 22, 2020
@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Mar 23, 2020
@ghost ghost added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels May 23, 2020
@vlerenc vlerenc added roadmap/internal and removed lifecycle/rotten Nobody worked on this for 12 months (final aging stage) labels Sep 26, 2020
@vlerenc vlerenc modified the milestones: 0.9.0, 2021-Q1 Sep 26, 2020
@amshuman-kr
Copy link
Collaborator

Moved to gardener/etcd-druid#107

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/backup Backup related area/disaster-recovery Disaster recovery related component/etcd-backup-restore ETCD Backup & Restore kind/enhancement Enhancement, improvement, extension topology/garden Affects Garden clusters topology/seed Affects Seed clusters
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants