Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 2. Installing Red Hat Developer Hub in an air-gapped environment with the Operator

You can install Red Hat Developer Hub in a fully disconnected or partially disconnected environment using the Red Hat Developer Hub Operator. For a list of supported platforms, see the Red Hat Developer Hub Life Cycle page.

In environments without internet access — whether for security, compliance, or operational reasons — a fully disconnected installation ensures that Red Hat Developer Hub can run reliably without external dependencies.

If your network has access to the registry through a bastion host, you can use the helper script to install Red Hat Developer Hub by mirroring the Operator-related images to disk and transferring them to your air-gapped environment without any connection to the internet.

Prerequisites

  • You have installed Podman 5.3 or later. For more information, see Podman Installation Instructions.
  • You have installed Skopeo 1.17 or later.
  • You have installed yq 4.44 or later.
  • You have installed the GNU sed command line text editor.
  • You have installed umoci CLI tool.
  • You have an active oc registry, podman, or skopeo session to the registry.redhat.io Red Hat Ecosystem Catalog. For more information, see link:Red Hat Container Registry Authentication.
  • You have installed the opm CLI tool. For more information, see {ocp-docs-link}/html/cli_tools/opm-cli#olm-about-opm_cli-opm-install[Installing the opm CLI].
  • Make sure that your system meets the minimum sizing requirements. See Sizing requirements for Red Hat Developer Hub.

Procedure

  1. Download the mirroring script to disk by running the following command: 

    curl -sSLO https://raw.githubusercontent.com/redhat-developer/rhdh-operator/refs/heads/release-1.6/.rhdh/scripts/prepare-restricted-environment.sh
    Copy to Clipboard Toggle word wrap

  2. Run the mirroring script by using the bash command with the appropriate set of options: 

    bash prepare-restricted-environment.sh
 --filter-versions "1.6"
 --to-dir _<my_pulled_image_location>_
    1 
    
 [--use-oc-mirror true]
    2
    Copy to Clipboard Toggle word wrap
    1
    Specifies the absolute path to a directory where you want to pull all of the necessary images with the --to-dir option, for example, /home/user/rhdh-operator-mirror-dir.
    2
    (Optional) Uses the oc-mirror OpenShift Container Platform CLI plugin to mirror images.
    Note

    The script can take several minutes to complete as it copies multiple images to the mirror registry.

  3. Transfer the directory specified by the --to-dir option to your disconnected environment.

  4. 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: 

    bash <my_pulled_image_location>/install.sh
    1 
    
    --from-dir <my_pulled_image_location>
    2 
    
    [--to-registry <my.registry.example.com>]
    3 
    
    [--use-oc-mirror true]
    4
    Copy to Clipboard Toggle word wrap
    1
    The downloaded image and the absolute path to the directory where it is stored on your system.
    2
    Specifies the directory where you want to pull all of the necessary images with the --to-dir option.
    3
    Specifies the URL for the target mirror registry where you want to mirror the images.
    4
    (Optional) Uses the oc-mirror OpenShift Container Platform CLI plugin to mirror images.
    Important

    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.

    Note

    The script can take several minutes to complete as it automatically installs the Red Hat Developer Hub Operator.

Verification

  • If you are using Red Hat OpenShift Container Platform, the Red Hat Developer Hub Operator is in the Installed Operators list in the web console.

  • If you are using a supported Kubernetes platform, you can check the list of pods running in the rhdh-operator namespace by running the following command in your terminal: 

    kubectl -n rhdh-operator get pods
    Copy to Clipboard Toggle word wrap

Next steps

On an OpenShift Container Platform cluster operating on a restricted network, public resources are not available. However, deploying the Red Hat Developer Hub Operator and running Developer Hub requires the following public resources:

  • Operator images (bundle, operator, catalog)
  • Operands images (RHDH, PostgreSQL)

To make these resources available, replace them with their equivalent resources in a mirror registry accessible to your cluster.

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 Red Hat Developer Hub Operator and creating Developer Hub 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 OpenShift Container Platform cluster, you might want to expose and leverage the internal cluster registry.

When connected to a OpenShift Container Platform 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.

Prerequisites

  • You have installed Podman 5.3 or later. For more information, see Podman Installation Instructions.
  • You have installed Skopeo 1.17 or later.
  • You have installed yq 4.44 or later.
  • You have installed the GNU sed command line text editor.
  • You have installed umoci CLI tool.
  • You have an active oc registry, podman, or skopeo session to the registry.redhat.io Red Hat Ecosystem Catalog. For more information, see Red Hat Container Registry Authentication.
  • You have an active skopeo session with administrative access to the target mirror registry. For more information, see Authenticating to a registry.
  • You have installed the opm CLI tool. For more information, see Installing the opm CLI.

  • If you are using an OpenShift Container Platform cluster, you have the following prerequisites:

    • (Optional) You have installed the oc-mirror OpenShift Container Platform CLI plugin if you want to use it to mirror images.

  • If you are using a supported Kubernetes cluster, you have the following prerequisites:

    • You have installed the Operator Lifecycle Manager (OLM) on the disconnected cluster.
    • You have a mirror registry that is reachable from the disconnected cluster.
  • Make sure that your system meets the minimum sizing requirements. See Sizing requirements for Red Hat Developer Hub.

Procedure

  1. In your terminal, navigate to the directory where you want to save the mirroring script.

  2. Download the mirroring script by running the following command: 

    curl -sSLO https://raw.githubusercontent.com/redhat-developer/rhdh-operator/refs/heads/release-1.6/.rhdh/scripts/prepare-restricted-environment.sh
    Copy to Clipboard Toggle word wrap

  3. Run the mirroring script by using the bash command with the appropriate set of options: 

    bash prepare-restricted-environment.sh \
 --filter-versions "1.6" \
  [--to-registry <my.registry.example.com>] \
    1 
    
  [--use-oc-mirror true]
    2
    Copy to Clipboard Toggle word wrap
    1
    Specifies the URL for the target mirror registry where you want to mirror the images.
    2
    (Optional) Uses the oc-mirror OpenShift Container Platform CLI plugin to mirror images.
    Note

    The script can take several minutes to complete as it copies multiple images to the mirror registry.

Verification

  • If you are using Red Hat OpenShift Container Platform, the Red Hat Developer Hub Operator is in the Installed Operators list in the web console.

  • If you are using a supported Kubernetes platform, you can check the list of pods running in the rhdh-operator namespace by running the following command in your terminal: 

    kubectl -n rhdh-operator get pods
    Copy to Clipboard Toggle word wrap

Next steps

Retour au début
Red Hat logoGithubredditYoutubeTwitter

Apprendre

Essayez, achetez et vendez

Communautés

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Theme

© 2025 Red Hat