user81230
6 months ago
committed by
GitHub
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with
3 additions and
2 deletions
-
docs/recover-control-plane.md
|
|
|
@ -8,6 +8,7 @@ Examples of what broken means in this context: |
|
|
|
* One or more bare metal node(s) suffer from unrecoverable hardware failure |
|
|
|
* One or more node(s) fail during patching or upgrading |
|
|
|
* Etcd database corruption |
|
|
|
|
|
|
|
* Other node related failures leaving your control plane degraded or nonfunctional |
|
|
|
|
|
|
|
__Note that you need at least one functional node to be able to recover using this method.__ |
|
|
|
@ -16,8 +17,8 @@ __Note that you need at least one functional node to be able to recover using th |
|
|
|
|
|
|
|
* Backup what you can |
|
|
|
* Provision new nodes to replace the broken ones |
|
|
|
* Move any broken etcd nodes into the "broken\_etcd" group, make sure the "etcd\_member\_name" variable is set. |
|
|
|
* Move any broken control plane nodes into the "broken\_kube\_control\_plane" group. |
|
|
|
* Copy any broken etcd nodes into the "broken\_etcd" group, make sure the "etcd\_member\_name" variable is set. |
|
|
|
* Copy any broken control plane nodes into the "broken\_kube\_control\_plane" group. |
|
|
|
* Place the surviving nodes of the control plane first in the "etcd" and "kube\_control\_plane" groups |
|
|
|
* Add the new nodes below the surviving control plane nodes in the "etcd" and "kube\_control\_plane" groups |
|
|
|
|
|
|
|
|
