From 4cf2e8e4cb007e84b7d429421ac4669401dfba9f Mon Sep 17 00:00:00 2001 From: Roman Mazurenko Date: Mon, 15 Jun 2020 23:34:04 +0300 Subject: [PATCH] Clarify imagePullPolicy for empty value imagePullPolicy when defined without a value defaults to Always not to IfNotPresent --- content/en/docs/concepts/containers/images.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/concepts/containers/images.md b/content/en/docs/concepts/containers/images.md index 47f395841a..b50180b850 100644 --- a/content/en/docs/concepts/containers/images.md +++ b/content/en/docs/concepts/containers/images.md @@ -61,6 +61,8 @@ you can do one of the following: - omit the `imagePullPolicy` and the tag for the image to use. - enable the [AlwaysPullImages](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages) admission controller. +When `imagePullPolicy` is defined without a specific value, it is also set to `Always`. + ## Multi-architecture Images with Manifests 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 architecturew-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.