whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #24728 from nate-double-u/23055-copy-update

Browse Source 
Copy updates for k8s.io/docs/concepts/containers/images/
This commit is contained in:
Kubernetes Prow Robot
2020-10-29 14:18:06 -07:00
committed by GitHub
parent e88749b00a 9a6731fc8b
commit 7ffb2882df
1 changed files with 9 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/containers/images.md
+9 -9
View File
@@ -47,7 +47,7 @@ to roll back to a working version.
Instead, specify a meaningful tag such as `v1.42.0`. Instead, specify a meaningful tag such as `v1.42.0`.
{{< /caution >}} {{< /caution >}}
## Updating Images ## Updating images
The default pull policy is `IfNotPresent` which causes the The default pull policy is `IfNotPresent` which causes the
{{< glossary_tooltip text="kubelet" term_id="kubelet" >}} to skip {{< glossary_tooltip text="kubelet" term_id="kubelet" >}} to skip
@@ -61,13 +61,13 @@ you can do one of the following:
When `imagePullPolicy` is defined without a specific value, it is also set to `Always`. When `imagePullPolicy` is defined without a specific value, it is also set to `Always`.
## Multi-architecture Images with Manifests ## Multi-architecture images with image indexes
As well as providing binary images, a container registry can also serve 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 a 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. As well as providing binary images, a container registry can also serve a [container image index](https://github.com/opencontainers/image-spec/blob/master/image-index.md). An image index can point to multiple [image manifests](https://github.com/opencontainers/image-spec/blob/master/manifest.md) for architecture-specific versions of a 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.
Kubernetes itself typically names container images with a suffix `-$(ARCH)`. For backward compatibility, please generate the older images with suffixes. The idea is to generate say `pause` image which has the manifest for all the arch(es) and say `pause-amd64` which is backwards compatible for older configurations or YAML files which may have hard coded the images with suffixes. Kubernetes itself typically names container images with a suffix `-$(ARCH)`. For backward compatibility, please generate the older images with suffixes. The idea is to generate say `pause` image which has the manifest for all the arch(es) and say `pause-amd64` which is backwards compatible for older configurations or YAML files which may have hard coded the images with suffixes.
## Using a Private Registry ## Using a private registry
Private registries may require keys to read images from them. Private registries may require keys to read images from them.
Credentials can be provided in several ways: Credentials can be provided in several ways:
@@ -86,7 +86,7 @@ Credentials can be provided in several ways:
These options are explaind in more detail below. These options are explaind in more detail below.
### Configuring Nodes to authenticate to a Private Registry ### Configuring nodes to authenticate to a private registry
If you run Docker on your nodes, you can configure the Docker container If you run Docker on your nodes, you can configure the Docker container
runtime to authenticate to a private container registry. runtime to authenticate to a private container registry.
@@ -178,7 +178,7 @@ template needs to include the `.docker/config.json` or mount a drive that contai
All pods will have read access to images in any private registry once private All pods will have read access to images in any private registry once private
registry keys are added to the `.docker/config.json`. registry keys are added to the `.docker/config.json`.
### Pre-pulled Images ### Pre-pulled images
{{< note >}} {{< note >}}
This approach is suitable if you can control node configuration. It This approach is suitable if you can control node configuration. It
@@ -197,7 +197,7 @@ This can be used to preload certain images for speed or as an alternative to aut
All pods will have read access to any pre-pulled images. All pods will have read access to any pre-pulled images.
### Specifying ImagePullSecrets on a Pod ### Specifying imagePullSecrets on a Pod
{{< note >}} {{< note >}}
This is the recommended approach to run containers based on images This is the recommended approach to run containers based on images
@@ -206,7 +206,7 @@ in private registries.
Kubernetes supports specifying container image registry keys on a Pod. Kubernetes supports specifying container image registry keys on a Pod.
#### Creating a Secret with a Docker Config #### Creating a Secret with a Docker config
Run the following command, substituting the appropriate uppercase values: Run the following command, substituting the appropriate uppercase values:
@@ -266,7 +266,7 @@ Check [Add ImagePullSecrets to a Service Account](/docs/tasks/configure-pod-cont
You can use this in conjunction with a per-node `.docker/config.json`. The credentials You can use this in conjunction with a per-node `.docker/config.json`. The credentials
will be merged. will be merged.
## Use Cases ## Use cases
There are a number of solutions for configuring private registries. Here are some There are a number of solutions for configuring private registries. Here are some
common use cases and suggested solutions. common use cases and suggested solutions.