kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add small note about rotating cluster after backup restore

This commit is contained in:
Ole Markus With 2021-06-10 09:08:04 +02:00
parent 0d63479723
commit fea2a08b1c
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/operations/etcd_backup_restore_encryption.md
View File

@ -92,7 +92,13 @@ After that, you can check again the endpoint and everything should be fixed.
After the restore is complete, api server should come back up, and you should have a working cluster.
Note that the api server might be very busy for a while as it changes the cluster back to the state of the backup.
It's a good idea to temporarily increase the instance size of your masters and roll your worker nodes.
You can consider temporarily increase the instance size of your masters and roll your worker nodes.
Because the state on each of the Nodes may differ from the state in etcd, it is also a good idea to do a rolling-update of the entire cluster:
```sh
kops rolling-update cluster --force --yes
```
For more information and troubleshooting, please check the [etcd-manager documentation](https://github.com/kopeio/etcd-manager).