Skip to content
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.

Sign up for GitHub

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

Jump to bottom

https://issues.redhat.com/browse/ACM-14437 #7230

Open
wants to merge 1 commit into
base: 2.9_stage
Choose a base branch
from
Open

https://issues.redhat.com/browse/ACM-14437 #7230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 23 additions & 3 deletions clusters/cluster_lifecycle/release_image_disconn.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ In some cases, you need to maintain a custom list of release images when the hub

. Add the YAML files for the images that you want available when you create a cluster by using the console or CLI to manually add the `clusterImageSet` YAML content.

. Modify the `clusterImageSet` YAML files for the remaining {ocp-short} release images to reference the correct offline repository where you store the images. Your updates resemble the following example where `spec.releaseImage` refers to the image registry that you are using:
. Modify the `clusterImageSet` YAML files for the remaining {ocp-short} release images to reference the correct offline repository where you store the images. Your updates resemble the following example where `spec.releaseImage` refers to the image registry or digest that you are using:

+
[source,yaml]
Expand All @@ -27,12 +27,32 @@ metadata:
channel: fast
name: img4.13.8-x86-64-appsub
spec:
releaseImage: IMAGE_REGISTRY_IPADDRESS_or_DNSNAME/REPO_PATH/ocp-release:4.12.8-x86_64
releaseImage: IMAGE_REGISTRY_IPADDRESS_or__DNSNAME/REPO_PATH/ocp-release@sha256:073a4e46289be25e2a05f5264c8f1d697410db66b960c9ceeddebd1c61e58717
----

. Ensure that the images are loaded in the offline image registry that is referenced in the YAML file.

. To use digest, obtain the image digest by running the following command:

+
Ensure that the images are loaded in the offline image registry that is referenced in the YAML file.
[source,bash]
----
oc adm release info <tagged_openshift_release_image> | grep "Pull From"
----
+
Replace `<tagged_openshift_release_image>` with the tagged image for the supported {ocp-short} version. See the following example output:

+
[source,bash]
----
Pull From: quay.io/openshift-release-dev/ocp-release@sha256:69d1292f64a2b67227c5592c1a7d499c7d00376e498634ff8e1946bc9ccdddfe
----

+
To learn more about the image tag and digest, see link:https://docs.redhat.com/documentation/en-us/openshift_container_platform/4.14/html/images/managing-images#images-referencing-images-imagestreams_tagging-images[Referencing images in imagestreams].

. Create each of the `clusterImageSets` by entering the following command for each YAML file:

+
----
oc create -f <clusterImageSet_FILE>
Expand Down