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

Update keypair rotation documentation

This commit is contained in:
John Gardiner Myers 2021-07-15 14:05:08 -07:00
parent 3ae5413f63
commit 1d3bdf54af
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/operations/rotate-secrets.md
View File

@ -1,3 +1,4 @@
# How to rotate all secrets / credentials # How to rotate all secrets / credentials
There are two types of credentials managed by kOps: There are two types of credentials managed by kOps:
@ -71,11 +72,15 @@ Promote the new keypairs to primary with:
```shell ```shell
kops promote keypair all kops promote keypair all
kops update cluster --yes kops update cluster --yes
kops rolling-update cluster --force --yes kops rolling-update cluster --yes
``` ```
As of the writing of this document, rolling-update will not necessarily identify all On cloud providers, such as AWS, that use kops-controller to bootstrap worker nodes, after
relevant nodes as needing update, so should be invoked with the `--force` flag. the `kops update cluster --yes` step there is a temporary impediment to node scale-up.
Instances using the new launch template will not be able to bootstrap off of old kops-controllers.
Similarly, instances using the old launch template and which have not yet bootstrapped will not
be able to bootstrap off of new kops-controllers. The subsequent rolling update will eventually
replace all instances using the old launch template.
#### Rollback procedure #### Rollback procedure
@ -89,7 +94,7 @@ To roll back this change:
most likely by identifying the issue dates. most likely by identifying the issue dates.
* Then use `kops promote keypair` to promote each of them by keyset and ID. * Then use `kops promote keypair` to promote each of them by keyset and ID.
* Then use `kops update cluster --yes` * Then use `kops update cluster --yes`
* Then use `kops rolling-update cluster --force --yes` * Then use `kops rolling-update cluster --yes`
### Export and distribute new kubeconfig admin credentials ### Export and distribute new kubeconfig admin credentials