From fea2a08b1ce8b1a1987939c59d0e70b6d0312c80 Mon Sep 17 00:00:00 2001 From: Ole Markus With Date: Thu, 10 Jun 2021 09:08:04 +0200 Subject: [PATCH 1/2] Add small note about rotating cluster after backup restore --- docs/operations/etcd_backup_restore_encryption.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/operations/etcd_backup_restore_encryption.md b/docs/operations/etcd_backup_restore_encryption.md index c3567a927d..abf63148b3 100644 --- a/docs/operations/etcd_backup_restore_encryption.md +++ b/docs/operations/etcd_backup_restore_encryption.md @@ -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 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). From 63f624764fa5b594742e9b4be45cc6c120045089 Mon Sep 17 00:00:00 2001 From: Ole Markus With Date: Fri, 11 Jun 2021 18:53:18 +0200 Subject: [PATCH 2/2] Update docs/operations/etcd_backup_restore_encryption.md Co-authored-by: John Gardiner Myers --- docs/operations/etcd_backup_restore_encryption.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/operations/etcd_backup_restore_encryption.md b/docs/operations/etcd_backup_restore_encryption.md index abf63148b3..6ddb172114 100644 --- a/docs/operations/etcd_backup_restore_encryption.md +++ b/docs/operations/etcd_backup_restore_encryption.md @@ -92,7 +92,7 @@ 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. -You can consider temporarily increase the instance size of your masters and roll your worker nodes. +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: