-
Notifications
You must be signed in to change notification settings - Fork 1.8k
OSDOCS:14467 [GA] Pin and preload images #92741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
🤖 Mon Jun 02 16:37:46 - Prow CI generated the docs preview: |
@RishabhSaini @ptalgulk01 Can you PTAL? |
LGTM |
8392d3d
to
cba21c2
Compare
4134771
to
1dd02bd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good! Just a few questions and comments -- in particular, about whether to write "preload and pin" or "pin and preload".
machine_configuration/machine-config-pin-preload-images-about.adoc
Outdated
Show resolved
Hide resolved
machine_configuration/machine-config-pin-preload-images-about.adoc
Outdated
Show resolved
Hide resolved
machine_configuration/machine-config-pin-preload-images-about.adoc
Outdated
Show resolved
Hide resolved
machine_configuration/machine-config-pin-preload-images-about.adoc
Outdated
Show resolved
Hide resolved
machine_configuration/machine-config-pin-preload-images-about.adoc
Outdated
Show resolved
Hide resolved
a075707
to
b111c97
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/label peer-review-in-progress
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/remove-label peer-review-needed
/remove-label peer-review-in-progress
/label peer-review-done
/lgtm
|
||
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. | ||
Pinned images also ensures that the images are available when deploying applications, so that you can deploy in a predictable time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just curious: When you say "predictable time", does this mean that this feature will give an accurate time for deployment, or it speeds up the deployment time...maybe both?
|
||
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: | ||
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if there is info missing in the second sentence? Unclear about what "..on those" means.
@mburke5678 , Great job on this doc. Just had a couple of comments...and please remember to squash commits. Thanks! |
b111c97
to
76dc159
Compare
New changes are detected. LGTM label has been removed. |
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
The This is because your PR targets the If the update in your PR does NOT apply to version 4.20 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Currently (5/7) planned for a 4.19.z release
https://issues.redhat.com/browse/OSDOCS-14467
https://issues.redhat.com/browse/MCO-1258
QE review:
PEER REVIEW REQUEST 5/30. Please review the changes in this commit, where I changed the name and other details. The technical details have been peer-reviewed.