-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Specifying that disaster recovery requires a healthy node #34218
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
Specifying that disaster recovery requires a healthy node #34218
Conversation
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: df221cd 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/60ddcebfee8d2700078d9171 😎 Browse the preview: https://deploy-preview-34218--osdocs.netlify.app |
|
||
[IMPORTANT] | ||
==== | ||
Disaster recovery requires you to have at least one healthy master host. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/master/control-plane?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We do use "master host" mostly throughout these docs, so I don't want to introduce it in just this change. We do have efforts planned to s/master/control plane throughout the entire doc set coming down the line
.Prerequisites | ||
|
||
* Access to the cluster as a user with the `cluster-admin` role. | ||
* A healthy master host to use as the recovery host. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same
LGTM |
@vikram-redhat @sjstout Requesting a merge exception on this PR. It will still need QE overnight tonight, so it won't make freeze. But these are important statements to clarify, for SNO. |
LGTM |
LGTM, and i think this declaration is necessary, because we have doc bug about this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1860861 |
QE and Peer review done. Exception granted. Merging. |
/cherrypick enterprise-4.5 |
/cherrypick enterprise-4.6 |
@vikram-redhat: new pull request created: #34318 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. |
/cherrypick enterprise-4.7 |
@vikram-redhat: new pull request created: #34319 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. |
/cherrypick enterprise-4.8 |
@vikram-redhat: new pull request created: #34320 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. |
@vikram-redhat: new pull request created: #34321 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. |
Per @hexfusion
https://issues.redhat.com/browse/ETCD-125
Previews: