Skip to content

[enterprise-4.11] OSDOCS-5567: replacing OSUS mirroring admonition #57881

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

Merged
mburke5678 merged 1 commit into from
Mar 28, 2023
Merged

[enterprise-4.11] OSDOCS-5567: replacing OSUS mirroring admonition #57881

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
33 changes: 32 additions & 1 deletion modules/update-mirror-repository.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,11 @@
[id="update-mirror-repository-adm-release-mirror_{context}"]
= Mirroring images using the oc adm release mirror command

[IMPORTANT]
====
To avoid excessive memory usage by the OpenShift Update Service application, you must mirror release images to a separate repository as described in the following procedure.
====

.Prerequisites

* You configured a mirror registry to use in your disconnected environment and can access the certificate and credentials that you configured.
Expand Down Expand Up @@ -52,6 +57,16 @@ $ LOCAL_REPOSITORY='<local_repository_name>'
For `<local_repository_name>`, specify the name of the repository to create in your
registry, such as `ocp4/openshift4`.

.. If you are using the OpenShift Update Service, export an additional local repository name to contain the release images:
+
[source,terminal]
----
$ LOCAL_RELEASE_IMAGES_REPOSITORY='<local_release_images_repository_name>'
----
+
For `<local_release_images_repository_name>`, specify the name of the repository to
create in your registry, such as `ocp4/openshift4-release-images`.

.. Export the name of the repository to mirror:
+
[source,terminal]
Expand Down Expand Up @@ -134,7 +149,16 @@ $ oc apply -f ${REMOVABLE_MEDIA_PATH}/mirror/config/<image_signature_file> <1>
+
<1> For `<image_signature_file>`, specify the path and name of the file, for example, `signature-sha256-81154f5c03294534.yaml`.

** If the local container registry and the cluster are connected to the mirror host, directly push the release images to the local registry and apply the config map to the cluster by using following command:
... If you are using the OpenShift Update Service, mirror the release image to a separate repository:
+
[source,terminal]
----
$ oc image mirror -a ${LOCAL_SECRET_JSON} ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE} ${LOCAL_REGISTRY}/${LOCAL_RELEASE_IMAGES_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE}
----

** If the local container registry and the cluster are connected to the mirror host, take the following actions:

... Directly push the release images to the local registry and apply the config map to the cluster by using following command:
+
[source,terminal]
----
Expand All @@ -146,3 +170,10 @@ $ oc adm release mirror -a ${LOCAL_SECRET_JSON} --from=quay.io/${PRODUCT_REPO}/$
====
If you include the `--apply-release-image-signature` option, do not create the config map for image signature verification.
====

... If you are using the OpenShift Update Service, mirror the release image to a separate repository:
+
[source,terminal]
----
$ oc image mirror -a ${LOCAL_SECRET_JSON} ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE} ${LOCAL_REGISTRY}/${LOCAL_RELEASE_IMAGES_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE}
----