From 52c255c9087e97a0cc31780167ada49ae152a61b Mon Sep 17 00:00:00 2001 From: Bjarke Vad Andersen Date: Wed, 9 Nov 2016 10:02:47 +0100 Subject: [PATCH] Use correct `kops rolling-update` command --- docs/security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/security.md b/docs/security.md index 754d0e8551..520c9a92bd 100644 --- a/docs/security.md +++ b/docs/security.md @@ -16,7 +16,7 @@ To change the SSH public key on an existing cluster: * `kops delete secret --name sshpublickey admin` * `kops create secret --name sshpublickey admin -i ~/.ssh/newkey.pub` * `kops update cluster --yes` to reconfigure the auto-scaling groups -* `kops rolling-update --yes` to immediately roll all the machines so they have the new key (optional) +* `kops rolling-update cluster --name --yes` to immediately roll all the machines so they have the new key (optional) ## Kubernetes API