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
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -684,8 +684,8 @@ for information on referencing service account credentials from within Pods.
684
684
685
685
### Docker config Secrets
686
686
687
-
You **MUST** use one of the following `type` values to create a Secret to
688
-
store the credentials for accessing a container image registry:
687
+
If you are creating a Secret to store credentials for accessing a container image registry,
688
+
you must use one of the following `type` values for that Secret:
689
689
690
690
- `kubernetes.io/dockercfg`
691
691
- `kubernetes.io/dockerconfigjson`
@@ -761,10 +761,12 @@ Docker configuration file):
761
761
}
762
762
```
763
763
764
-
{{< note >}}
764
+
{{< caution >}}
765
765
The `auth` value there is base64 encoded; it is obscured but not secret.
766
766
Anyone who can read that Secret can learn the registry access bearer token.
767
-
{{< /note >}}
767
+
768
+
It is suggested to use [credential providers](/docs/tasks/administer-cluster/kubelet-credential-provider/) to dynamically and securely provide pull secrets on-demand.
0 commit comments