Chapter 17. Airgapped environment

download PDF

An air-gapped environment ensures security by physically isolating it from other networks and systems. You can install director Operator in an air-gapped environment to ensure security and provides certain regulatory requirements.

17.1. Prerequisites

  • An operational Red Hat Openshift Container Platform (RHOCP) cluster, version 4.12 or later. The cluster must contain a provisioning network, and the following Operators:

  • You have a disconnected registry adhering to docker v2 schema. For more information, see Mirroring images for a disconnected installation.
  • You have access to a Satellite server or any other repository used to register the overcloud nodes and install packages.
  • The oc command line tool is installed on your workstation.
  • You have access to a local git repository to store deployment artifacts.
  • You have installed the podman and skopeo command line tools on your workstation.

17.2. Configuring an airgapped environment

To configure an airgapped environment, you must have access to both and the registry for airgapped environment. For more information on how to access both registries, see Mirroring catalog contents to airgapped registries.


  1. Create the openstack namespace:

    $ oc new-project openstack
  2. Create the index image and push it to your registry:

    $ podman login
    $ podman login your.registry.local
    $ BUNDLE_IMG=""

    You can get the latest bundle image from: Certified container images. Search for osp-director-operator-bundle.

  3. Mirror the relevant images based on the operator index image:

    $ oc adm catalog mirror ${INDEX_IMG} your.registry.local --insecure --index-filter-by-os='Linux/x86_64'
  4. After mirroring is complete, a manifests directory is generated in your current directory called manifests-osp-director-operator-index-<random_number>. Apply the created ImageContentSourcePolicy to your cluster:

    $ os apply -f manifests-osp-director-operator-index-<random_number>/imageContentSourcePolicy.yaml
    • Replace <random_number> with the randomly generated number.
  5. Create a file named osp-director-operator.yaml and include the following YAML content to configure the three resources required to install director Operator:

    kind: CatalogSource
      name: osp-director-operator-index
      namespace: openstack
      sourceType: grpc
      image: your.registry.local/osp-director-operator-index:1.3.x-y
    kind: OperatorGroup
      name: "osp-director-operator-group"
      namespace: openstack
      - openstack
    kind: Subscription
      name: osp-director-operator-subscription
      namespace: openstack
        - name: WATCH_NAMESPACE
          value: openstack,openshift-machine-api,openshift-sriov-network-operator
      source: osp-director-operator-index
      sourceNamespace: openstack
      name: osp-director-operator
  6. Create the new resources in the openstack namespace:

    $ oc apply -f osp-director-operator.yaml
  7. Copy the required overcloud images to the repository:

    $ for i in $(podman search --limit 1000 "" --format="{{ .Name }}" | awk '{print $1 ":" "17.1.0"}' | awk -F "/" '{print $2 "/" $3}'); do skopeo copy --all docker://$i docker://your.registry.local/$i;done

    You can refer to Preparing a Satellite server for container images if Red Hat Satellite is used as the local registry.

  8. You can now proceed with Installing and preparing director Operator.


  1. Confirm that you have successfully installed director Operator:

    $ oc get operators
    NAME                                     AGE
    osp-director-operator.openstack          5m
Red Hat logoGithubRedditYoutubeTwitter


Try, buy, & sell


About Red Hat Documentation

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

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.

© 2024 Red Hat, Inc.