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

docs: fix broken example command

This commit is contained in:
Markus Lehtonen 2024-01-11 09:01:43 +02:00 committed by GitHub
parent 7b631db949
commit f29f01f9f0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/security.md
View File

@ -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 <clustername> sshpublickey`
* `kops create sshpublickey --name <clustername> sshpublickey -i ~/.ssh/newkey.pub`
* `kops create sshpublickey --name <clustername> -i ~/.ssh/newkey.pub`
* `kops update cluster <clustername> --yes` to reconfigure the launch templates.
* `kops rolling-update cluster --name <clustername> --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.
Currently, permission scope is quite broad. See [iam_roles.md](iam_roles.md) for details and ways to mitigate that.