You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/concepts/configuration/secret.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,10 @@ also creates some Secrets.
28
28
Kubernetes Secrets are, by default, stored as unencrypted base64-encoded
29
29
strings. By default they can be retrieved - as plain text - by anyone with API
30
30
access, or anyone with access to Kubernetes' underlying data store, etcd. In
31
-
order to safely use Secrets, we recommend you (at a minimum):
31
+
order to safely use Secrets, it is recommended you (at a minimum):
32
32
33
-
1.[Enable Encryption at Rest](https://kubernetes.io/docs/tasks/administer-cluster/encrypt-data/) for Secrets.
34
-
2.[Enable RBAC rules that restrict reading and writing the Secret](https://kubernetes.io/docs/reference/access-authn-authz/authorization/). Be aware that secrets can be obtained implicitly by anyone with the permission to create a Pod.
33
+
1.[Enable Encryption at Rest](/docs/tasks/administer-cluster/encrypt-data/) for Secrets.
34
+
2.[Enable or configure RBAC rules](/docs/reference/access-authn-authz/authorization/) that restrict reading and writing the Secret. Be aware that secrets can be obtained implicitly by anyone with the permission to create a Pod.
0 commit comments