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 in disconnected environments of the Operators guide in OpenShift Container Platform documentation.

Note

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.

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 operator bundles for the OpenShift Data Foundation deployment:

  • ocs-operator
  • odf-operator
  • mcg-operator
  • odf-csi-addons-operator
  • ocs-client-operator
  • odf-prometheus-operator
  • recipe
  • rook-ceph-operator
  • cephcsi-operator
  • odf-dependencies

Only for local storage deployments:

  • local-storage-operator

Only for Regional Disaster Recovery (Regional-DR) configuration or Metro Disaster Recovery (Metro-DR) configuration:

  • odf-multicluster-orchestrator
  • odr-cluster-operator
  • odr-hub-operator
Important

Make sure to name the CatalogSource as redhat-operators.

Upgrade requirements

When mirroring OpenShift Data Foundation for y-stream upgrades in a disconnected environment, ensure the following:

  • Include all the OpenShift Data Foundation operator bundles in the mirror configuration file.
  • Package both operator versions, the currently installed version and the target upgrade version within the same operator catalog index image.

    For example:

    - name: odf-operator
      channels:
      - name: stable-<target-odf-version>
        minVersion : <target-upgrade-version>-rhodf
        maxVersion : <target-upgrade-version>-rhodf
      - name: stable-<current-odf-version>
        minVersion : <current-version>-rhodf
        maxVersion : <current-version>-rhodf
    - name: ocs-operator
      channels:
    [...]
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat