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: content/storage/ibm-fusion-access-san/index.md
+80Lines changed: 80 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,6 +118,86 @@ In my virtual lab environment running on KVM/libvirt with [hetzner-ocp4](https:/
118
118
Subject: CN=Organization signing key
119
119
```
120
120
121
+
## In case you want to run this in a disconnected/air-gapped environment
122
+
123
+
In a disconnected environment, you need to mirror the required container images to your local registry. This includes the IBM Fusion Access for SAN operator, the Kernel Module Management (KMM) operator, and the specific IBM Spectrum Scale images.
124
+
125
+
### Mirroring images via oc-mirror v2
126
+
127
+
Use [oc-mirror v2](https://docs.redhat.com/en/documentation/openshift_container_platform/4.21/html/disconnected_environments/about-installing-oc-mirror-v2) to mirror the images.
After mirroring, apply the generated `CatalogSource`, `ImageContentSourcePolicy` (or `ImageDigestMirrorSet`), and `ImageTagMirrorSet` as usual.
194
+
195
+
### Important: Internal Registry for Kernel Module Builds
196
+
197
+
IBM Fusion Access for SAN uses KMM to build kernel modules on the fly. In a disconnected environment, you **must** provide a registry where KMM can push the newly built images and where the nodes can pull them from.
198
+
199
+
Refer to the [Configure external registry for kernel module container image](#optional-configure-external-registry-for-kernel-module-container-image) section for details on how to set this up. In a disconnected environment, this "external" registry would be your local/internal registry (e.g., Quay, Harbor, or the OpenShift integrated registry).
0 commit comments