Chapter 10. Disconnected environment
Disconnected environment is a network restricted environment where the Operator Lifecycle Manager (OLM) cannot access the default Operator Hub and image registries, which require internet connectivity.
Red Hat supports deployment of OpenShift Data Foundation in disconnected environments where you have installed OpenShift Container Platform in restricted networks.
To install OpenShift Data Foundation in a disconnected environment, see Using Operator Lifecycle Manager on restricted networks of the Operators guide in OpenShift Container Platform documentation.
When you install OpenShift Data Foundation in a restricted network environment, apply a custom Network Time Protocol (NTP) configuration to the nodes, because by default, internet connectivity is assumed in OpenShift Container Platform and chronyd is configured to use the *.rhel.pool.ntp.org servers.
For more information, see the Red Hat Knowledgebase solution A newly deployed OCS 4 cluster status shows as "Degraded", Why? and Configuring chrony time service of the Installing guide in OpenShift Container Platform documentation.
Red Hat OpenShift Data Foundation version 4.12 introduced the Agent-based Installer for disconnected environment deployment. The Agent-based Installer allows you to use a mirror registry for disconnected installations. For more information, see Preparing to install with Agent-based Installer.
Packages to include for OpenShift Data Foundation
When you prune the redhat-operator index image, include the following list of packages for the OpenShift Data Foundation deployment:
-
ocs-operator -
odf-operator -
mcg-operator -
odf-csi-addons-operator -
odr-cluster-operator -
odr-hub-operator Optional:
local-storage-operatorOnly for local storage deployments.
Optional:
odf-multicluster-orchestratorOnly for Regional Disaster Recovery (Regional-DR) configuration.
Name the CatalogSource as redhat-operators.
