Makes changes to image books as a result of ADV errors #103786
Conversation
openshift-ci
bot
added
the
size/L
|
🤖 Wed Dec 10 22:40:11 - Prow CI generated the docs preview: |
| ---- | ||
| + | ||
| For example, to configure the `ruby` image stream `static-2.0` tag to always refer to the current image for the `ruby` image stream `2.0` tag: | ||
| For example, to configure the `ruby` image stream `static-2.0` tag to always refer to the specific image that the `ruby:2.0` tag points to right now, enter the following command: |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'now' rather than 'right now'. For more information, see RedHat.TermsErrors.
| $ oc tag <source_reference> <destination_image_stream>:<destination_tag> --reference | ||
| ---- | ||
| * Optional: Use the `--reference-policy=local` flag to instruct {product-title} to always fetch the tagged image from the integrated registry. The registry uses the pull-through feature to serve the image to the client. By default, the image blobs are mirrored locally by the registry. As a result, they can be pulled more quickly the next time they are needed. The flag also allows for pulling from insecure registries without a need to supply `--insecure-registry` to the container runtime as long as the image stream has an insecure annotation or the tag has an insecure import policy. For example: |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'if' or 'provided that' rather than 'as long as'. For more information, see RedHat.TermsErrors.
| = Understanding image stream reference types | ||
|
|
||
| [role="_abstract"] | ||
| Image streams in {product-title} allow you to reference container images using different reference types. These reference types define which specific image version your builds and deployments utilize. |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'use' rather than 'utilize'. For more information, see RedHat.TermsErrors.
| .Procedure | ||
|
|
||
| * To reference an image for a given image stream and tag, use `ImageStreamTag`: | ||
| * To reference an image by a mutable tag (`ImageStreamTag`) from an image stream within your cluster, use the `<image_stream_name>:<tag>` format in your build or deployment configuration. For example: |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'deployment' rather than 'deployment configuration'. For more information, see RedHat.TermsErrors.
| .Procedure | ||
|
|
||
| * To reference an image for a given image stream and tag, use `ImageStreamTag`: | ||
| * To reference an image by a mutable tag (`ImageStreamTag`) from an image stream within your cluster, use the `<image_stream_name>:<tag>` format in your build or deployment configuration. For example: |
There was a problem hiding this comment.
🤖 [error] Vale.Avoid: Avoid using 'deployment configuration'.
| `image`:: Specifies the image to use from the image stream. For example, `ruby:2.0`. | ||
| -- | ||
|
|
||
| * To reference a specific, immutable image ID, or digest, within an image stream, use the `<image_stream_name>@<image_id>` format in your build or deployment configuration. For example: |
There was a problem hiding this comment.
🤖 [error] RedHat.TermsErrors: Use 'deployment' rather than 'deployment configuration'. For more information, see RedHat.TermsErrors.
| `image`:: Specifies the image to use from the image stream. For example, `ruby:2.0`. | ||
| -- | ||
|
|
||
| * To reference a specific, immutable image ID, or digest, within an image stream, use the `<image_stream_name>@<image_id>` format in your build or deployment configuration. For example: |
There was a problem hiding this comment.
🤖 [error] Vale.Avoid: Avoid using 'deployment configuration'.
|
@stevsmit: 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. |
3 participants
Version(s):
Issue:
Link to docs preview:
QE review:
Additional information: