Format security note with proper highlighting (#9942)
* Format security note with proper callout The information about security of ssh keys might benefit from standing out more. Thus included it in a caution shortcode. Formatting is now more aligned with the style guide. * close caution tagpull/10001/head
parent
d81c0c3cd5
commit
0ff0d79243
|
@ -482,7 +482,9 @@ Create a secret containing some ssh keys:
|
|||
$ kubectl create secret generic ssh-key-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub
|
||||
```
|
||||
|
||||
**Security Note:** Think carefully before sending your own ssh keys: other users of the cluster may have access to the secret. Use a service account which you want to be accessible to all the users with whom you share the Kubernetes cluster, and can revoke if they are compromised.
|
||||
{{< caution >}}
|
||||
**Caution:** Think carefully before sending your own ssh keys: other users of the cluster may have access to the secret. Use a service account which you want to be accessible to all the users with whom you share the Kubernetes cluster, and can revoke if they are compromised.
|
||||
{{< /caution >}}
|
||||
|
||||
|
||||
Now we can create a pod which references the secret with the ssh key and
|
||||
|
|
Loading…
Reference in New Issue