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
HOSTEDCP-1081: Perform etcd recovery when etcd member data is lost #2900
Conversation
@csrwng: This pull request references HOSTEDCP-1081 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
1 similar comment
@csrwng: This pull request references HOSTEDCP-1081 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: csrwng The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
When an etcd member's data has been lost, the only recourse we currently have is to do a hacky manual recovery. With this change, it is as simple as deleting the bad member's pvc and pod to restore a member.
/retest-required |
@csrwng: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/lgtm |
What this PR does / why we need it:
When an etcd member's data has been lost, the only recourse we currently have is to do a hacky manual recovery. With this change, it is as simple as deleting the bad member's pvc and pod to restore a member.
Automates the steps described in https://issues.redhat.com/browse/HOSTEDCP-1081
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Fixes #HOSTEDCP-1081
Checklist