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: machine_configuration/machine-config-pin-preload-images-about.adoc
+7-5Lines changed: 7 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,18 @@
1
1
:_mod-docs-content-type: ASSEMBLY
2
2
[id="machine-config-pin-preload-images-about"]
3
-
= About pre-loading and pinning images
3
+
= About pinned images
4
4
include::_attributes/common-attributes.adoc[]
5
5
:context: machine-config-operator
6
6
7
7
toc::[]
8
8
9
-
A slow, unreliable connection to an image registry can interfere with operations that require pulling images, such as updating a cluster or deploying an application. This can include clusters that have low bandwidth, clusters with unreliable internet connectivity, or clusters in a disconnected environment.
9
+
A slow, unreliable connection to an image registry can interfere with operations that require pulling images, such as updating a cluster or deploying an application. This can include clusters that have low bandwidth, clusters with unreliable internet connectivity, or clusters in a disconnected environment. For example, a cluster update might require pulling more than one hundred images. Failure to pull those images could cause retries that can interfere with the update process and might cause the update to fail.
10
10
11
-
For example, a cluster update might require pulling more than one hundred images. Failure to pull those images could cause retries that can interfere with the update process and might cause the update to fail. One way to prevent this is to _pre-load_ the required images by pulling them in advance, before they are actually needed. Then, by_pinning_them to a machine config pool, you ensure that the images are available when needed. Pre-loading and pinning images can provide a more consistent update, which is important when scheduling updates into maintenance windows.
11
+
One way to prevent this is to pull the required images in advance, before they are actually needed, and_pinning_those images to specific machine config pools. This ensures that the images are available to your nodes when needed. Pinned images can provide a more consistent update, which is important when scheduling updates into maintenance windows.
12
12
13
-
Pre-loading and pinning images also ensures that the images are available when deploying applications, so that you can deploy in a predictable time. Another benefit to pre-loading and pinning images is that image garbage collection does not remove the pinned images.
13
+
Pinned images also ensures that the images are available when deploying applications, so that you can deploy in a predictable time.
14
14
15
-
You can pre-load and pin images by using a a `PinnedImageSet` custom resource (CR), as described in _Pre-loading and pinning images_. Pinned images are stored on the nodes in the `/etc/crio/crio.conf.d/50-pinned-images` file. The contents of the file appear similar to the following example:
15
+
You can pin images to specific nodes by using a `PinnedImageSet` custom resource (CR), as described in _Pinning images_. Pinned images are stored on the nodes in the `/etc/crio/crio.conf.d/50-pinned-images` file on those. The contents of the file appear similar to the following example:
16
16
17
17
[source,terminal]
18
18
----
@@ -21,6 +21,8 @@ You can pre-load and pin images by using a a `PinnedImageSet` custom resource (C
Another benefit to pinned images is that image garbage collection does not remove the pinned images.
25
+
24
26
Before pulling the images, the Machine Config Operator (MCO) verifies that there is enough storage space available on each affected node. If the node has sufficient space, the MCO creates the pinned image file, pulls the images, and reloads CRI-O. If there is not sufficient space, the MCO does not pull the images and presents an error message.
You can pre-load and pin images by using a `PinnedImageSet` custom resource (CR). The pinned image set defines the list of images to pre-load and the machine config pool to which the images should be pinned.
9
+
You can pin images to your nodes by using a `PinnedImageSet` custom resource (CR). The pinned image set defines the list of images to pre-load and the machine config pool to which the images should be pinned.
10
10
11
11
The images are stored in the the `/etc/crio/crio.conf.d/50-pinned-images` file on the nodes.
0 commit comments