Add the accepted types for `imagePullSecrets`
This commit is contained in:
parent
bdadfbcf45
commit
6fb28754d4
|
|
@ -275,6 +275,8 @@ in private registries.
|
||||||
{{< /note >}}
|
{{< /note >}}
|
||||||
|
|
||||||
Kubernetes supports specifying container image registry keys on a Pod.
|
Kubernetes supports specifying container image registry keys on a Pod.
|
||||||
|
`imagePullSecrets` must all be in the same namespace as the Pod. The referenced
|
||||||
|
Secrets must be of type `kubernetes.io/dockercfg` or `kubernetes.io/dockerconfigjson`.
|
||||||
|
|
||||||
#### Creating a Secret with a Docker config
|
#### Creating a Secret with a Docker config
|
||||||
|
|
||||||
|
|
@ -303,7 +305,8 @@ so this process needs to be done one time per namespace.
|
||||||
#### Referring to an imagePullSecrets on a Pod
|
#### Referring to an imagePullSecrets on a Pod
|
||||||
|
|
||||||
Now, you can create pods which reference that secret by adding an `imagePullSecrets`
|
Now, you can create pods which reference that secret by adding an `imagePullSecrets`
|
||||||
section to a Pod definition.
|
section to a Pod definition. Each item in the `imagePullSecrets` array can only
|
||||||
|
reference a Secret in the same namespace.
|
||||||
|
|
||||||
For example:
|
For example:
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue