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

Merge pull request #11733 from olemarkus/docs-update-note 

Add small note about rotating cluster after backup restore
This commit is contained in:
Kubernetes Prow Robot 2021-06-11 11:09:01 -07:00 committed by GitHub
parent f5176c57ae 63f624764f
commit c2efa079a3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/operations/etcd_backup_restore_encryption.md
View File

@ -91,8 +91,14 @@ NOTE: You will need to run it multiple times for each old IP, regarding the size
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.
Note that the api server might be very busy for a while as it changes the cluster back to the state of the backup.
You might consider temporarily increasing the instance size of your control plane.
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).