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

[Feature] Enhance initialisation sequence according to the multi-node ETCD proposal #322

Closed
Tracked by #107
amshuman-kr opened this issue Apr 12, 2021 · 2 comments
Closed
Tracked by #107
Assignees
Labels
kind/enhancement Enhancement, improvement, extension release/beta Planned for Beta release of the Feature status/closed Issue is closed (either delivered or triaged)
Milestone

Comments

@amshuman-kr
Copy link
Collaborator

amshuman-kr commented Apr 12, 2021

Feature (What you would like to be added):

Enhance initialisation sequence according to the multi-node ETCD proposal.

This should including the following broad topics.

  1. Loading template etcd configuration (supplied by etcd-druid).
  2. Reading Status from the correspoding Etcd resource.
  3. Membership and data verification
  4. If necessary, removing old member and adding a new member
  5. If necessary, restoring from latest full snapshot
  6. If necessary, applying incremental snapshots
  7. If necessary, uploading a fresh snapshot (full or incremental)
  8. If necessary, generate fresh tailored etcd configuration for the corresponding member based on the supplied template configuration and other information from steps above so that the configuration can be used by the etcd container of the same member pod.

Motivation (Why is this needed?):

Pick individually executable pieces of the multi-node proposal.

Approach/Hint to the implement solution (optional):

@timuthy
Copy link
Member

timuthy commented Jan 14, 2022

/assign @abdasgupta
/touch

@ishan16696
Copy link
Member

Closing this issue in favour of these PRs: #419 ,gardener/etcd-custom-image#8, gardener/etcd-druid#193

/close

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension release/beta Planned for Beta release of the Feature status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Development

No branches or pull requests

6 participants