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: modules/installation/proc-install-rhdh-airgapped-environment-ocp-operator.adoc
+18-20Lines changed: 18 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,16 +16,16 @@ On an {ocp-short} cluster operating on a restricted network, public resources ar
16
16
17
17
To make these resources available, replace them with their equivalent resources in a mirror registry accessible to your cluster.
18
18
19
-
You can use a helper script that mirrors the necessary images and provides the necessary configuration to ensure those images will be used when installing the {product} Operator and creating {product-short} instances. This script requires a target mirror registry. You likely have a target mirror registry ready to use if your cluster is already operating on a disconnected network. If you do not already have a target registry, and if you have an {ocp-short} cluster, you might want to expose and leverage the internal cluster registry.
19
+
You can use a helper script that mirrors the necessary images and provides the necessary configuration to ensure those images are used when installing the {product} Operator and creating {product-short} instances. This script requires a target mirror registry. You likely have a target mirror registry if your cluster is already operating on a disconnected network. If you do not already have a target registry, and if you have an {ocp-short} cluster, you might want to expose and leverage the internal cluster registry.
20
20
21
-
If you are connected to a {ocp-short} cluster, the helper script will detect it and will automatically expose the cluster registry. However, if you are connected to a Kubernetes cluster, you can manually specify the target registry that you want to mirror the images to.
21
+
When connected to a {ocp-short} cluster, the helper script detects it and automatically exposes the cluster registry. If connected to a Kubernetes cluster, you can manually specify the target registry to mirror the images.
22
22
23
23
.Prerequisites
24
24
* You have installed Podman 5.3 or later. For more information, see link:https://podman.io/docs/installation[Podman Installation Instructions].
25
25
* You have installed Skopeo 1.17 or later.
26
-
* You have installed yq 4.44 or later.
27
-
* You have installed the GNU sed command line text editor.
28
-
* You have installed umoci CLI tool.
26
+
* You have installed `yq` 4.44 or later.
27
+
* You have installed the GNU `sed` command line text editor.
28
+
* You have installed `umoci` CLI tool.
29
29
* You have an active `oc registry`, `podman`, or `skopeo` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
30
30
* You have an active `skopeo` session with administrative access to the target mirror registry. For more information, see link:https://github.com/containers/skopeo#authenticating-to-a-registry[Authenticating to a registry].
31
31
* You have installed the `opm` CLI tool. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
@@ -44,7 +44,7 @@ If you are connected to a {ocp-short} cluster, the helper script will detect it
. Run the mirroring script by running the `bash` command with the appropriate set of options:
47
+
. Run the mirroring script by using the `bash` command with the appropriate set of options:
48
48
+
49
49
[source,terminal,subs="+quotes,+attributes"]
50
50
----
@@ -86,13 +86,11 @@ If your network has access to the registry through a bastion host, you can use t
86
86
87
87
* You have installed Podman 5.3 or later. For more information, see link:https://podman.io/docs/installation[Podman Installation Instructions].
88
88
* You have installed Skopeo 1.17 or later.
89
-
* You have installed yq 4.44 or later.
90
-
* You have installed the GNU sed command line text editor.
91
-
* You have installed umoci CLI tool.
89
+
* You have installed `yq` 4.44 or later.
90
+
* You have installed the GNU `sed` command line text editor.
91
+
* You have installed `umoci` CLI tool.
92
92
* You have an active `oc registry`, `podman`, or `skopeo` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
93
-
* You have an active `oc registry` session to the `registry.redhat.io` {company-name} Ecosystem Catalog. For more information, see link:https://access.redhat.com/RegistryAuthentication[{company-name} Container Registry Authentication].
94
93
* You have installed the `opm` CLI tool. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/4.17/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
95
-
* You have installed Podman 5.3 or later. For more information, see link:https://podman.io/docs/installation[Podman Installation Instructions].
96
94
97
95
.Procedure
98
96
. Download the mirroring script to disk by running the following command:
@@ -102,12 +100,12 @@ If your network has access to the registry through a bastion host, you can use t
. Run the mirroring script by running the `bash` command with the appropriate set of options:
103
+
. Run the mirroring script by using the `bash` command with the appropriate set of options:
106
104
+
107
-
[source,terminal,subs="+quotes,+attributes"]
105
+
[source,terminal,subs="attributes+"]
108
106
----
109
-
bash prepare-restricted-environment.sh \
110
-
--filter-versions "{product-version}" \
107
+
bash prepare-restricted-environment.sh
108
+
--filter-versions "{product-version}"
111
109
--to-dir _<my_pulled_image_location>_ <1>
112
110
[--use-oc-mirror true] <2>
113
111
----
@@ -120,21 +118,21 @@ The script can take several minutes to complete as it copies multiple images to
120
118
====
121
119
+
122
120
. Transfer the directory specified by the `--to-dir` option to your disconnected environment.
123
-
. From a machine in your disconnected environment that has access to both the cluster and the target mirror registry, run the mirroring script by running the `bash` command with the appropriate set of options:
121
+
. From a machine in your disconnected environment that has access to both the cluster and the target mirror registry, run the mirroring script by using the `bash` command with the appropriate set of options:
<1> The downloaded image and the absolute path to the directory where it is stored on your system.
133
131
<2> Specifies the directory where you want to pull all of the necessary images with the `--to-dir` option.
134
132
<3> Specifies the URL for the target mirror registry where you want to mirror the images.
135
133
<4> (Optional) Uses the `oc-mirror` {ocp-short} CLI plugin to mirror images.
136
134
+
137
-
[NOTE]
135
+
[IMPORTANT]
138
136
====
139
137
If you used `oc-mirror` to mirror the images to disk, you must also use `oc-mirror` to mirror the images from disk due to the folder layout that `oc-mirror` uses.
0 commit comments