Skip to content

Commit 01973ea

Browse files
authored
Merge pull request #21807 from rvmzes/master
Clarify imagePullPolicy for empty value
2 parents 67d40bc + 4cf2e8e commit 01973ea

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/en/docs/concepts/containers/images.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,8 @@ you can do one of the following:
6161
- omit the `imagePullPolicy` and the tag for the image to use.
6262
- enable the [AlwaysPullImages](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages) admission controller.
6363

64+
When `imagePullPolicy` is defined without a specific value, it is also set to `Always`.
65+
6466
## Multi-architecture Images with Manifests
6567

6668
As well as providing binary images, a container registry can also server a [container image manifest](https://github.com/opencontainers/image-spec/blob/master/manifest.md). A manifest can reference image manifests for architecture-specific versions of an container. The idea is that you can have a name for an image (for example: `pause`, `example/mycontainer`, `kube-apiserver`) and allow different systems to fetch the right binary image for the machine architecture they are using.

0 commit comments

Comments
 (0)