From f29f01f9f01a17a4183c1c86b6b0a57f1b5620b6 Mon Sep 17 00:00:00 2001 From: Markus Lehtonen <28872014+markusleh@users.noreply.github.com> Date: Thu, 11 Jan 2024 09:01:43 +0200 Subject: [PATCH] docs: fix broken example command --- docs/security.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/security.md b/docs/security.md index 091196927a..c163d78182 100644 --- a/docs/security.md +++ b/docs/security.md @@ -22,7 +22,7 @@ setting either `spec.sshAccess` in the cluster spec or using `kops create cluste To change the SSH public key on an existing cluster: * `kops delete sshpublickey --name sshpublickey` -* `kops create sshpublickey --name sshpublickey -i ~/.ssh/newkey.pub` +* `kops create sshpublickey --name -i ~/.ssh/newkey.pub` * `kops update cluster --yes` to reconfigure the launch templates. * `kops rolling-update cluster --name --yes` to roll all the machines so they have the new key. @@ -40,4 +40,4 @@ Note that this will also work when using containerd. ## Instance IAM roles All Pods running on your cluster have access to underlying instance IAM role. -Currently, permission scope is quite broad. See [iam_roles.md](iam_roles.md) for details and ways to mitigate that. \ No newline at end of file +Currently, permission scope is quite broad. See [iam_roles.md](iam_roles.md) for details and ways to mitigate that.