Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Chapter 5. Installing Orchestrator plugin in an air-gapped environment with the Operator

You can configure Red Hat Developer Hub (RHDH) with the Orchestrator plugin in a fully disconnected or partially disconnected environment by using the Operator.

You can install Red Hat Developer Hub with Orchestrator plugin in a fully air-gapped environment using the Operator.

A disconnected installation prevents unauthorized access, data transfer, or communication with external sources.

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 disconnected environment without any connection to the internet.

Prerequisites

  • You have mirrored the Red Hat Developer Hub Operator images to the local registry using the RHDH mirroring script. For more information, see Installing Red Hat Developer Hub in a fully disconnected environment with the Operator.
  • You have set up your disconnected environment using a local registry.
  • You have permissions to push NPM packages to an NPM server available in your restricted network.
  • You have installed the oc-mirror tool, with a version corresponding to the version of your OpenShift Container Platform cluster.

Procedure

  1. Create an ImageSetConfiguration file for oc-mirror. You must include the images and operators required by the Serverless Logic Operator in the ImageSetConfiguration file, as oc-mirror does not automatically mirror all images. Use the following example: 

    apiVersion: mirror.openshift.io/v2alpha1
kind: ImageSetConfiguration
mirror:
  additionalimages:
  - name: registry.redhat.io/openshift-serverless-1/logic-jobs-service-postgresql-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-jobs-service-ephemeral-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-data-index-postgresql-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-db-migrator-tool-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-swf-builder-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-swf-devmode-rhel8:1.36.0
  operators:
    - catalog: registry.redhat.io/redhat/redhat-operator-index:4.19
      # For example: registry.redhat.io/redhat/redhat-operator-index:v4.19
      packages:
      - name: logic-operator-rhel8
        channels:
        - name: alpha
          minVersion: 1.36.0
          maxVersion: 1.36.0
      - name: serverless-operator
        channels:
        - name: stable
          minVersion: 1.36.0
          maxVersion: 1.36.1

    Alternatively, you can use podman commands to find the missing images and add them to the additionalimages list if the versions change: 

    IMG=registry.redhat.io/openshift-serverless-1/logic-operator-bundle:1.36
mkdir local-manifests-osl
podman create --name temp-container "$IMG" -c "cat /manifests/logic-operator-rhel8.clusterserviceversion.yaml"
podman cp temp-container:/manifests ./local-manifests-osl
podman rm temp-container
yq -r '.data."controllers_cfg.yaml" | from_yaml | .. | select(tag == "!!str") | select(test("^.\\/.:.*$"))' ./local-manifests-osl/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml

  2. Mirror the images in the ImageSetConfiguration.yaml file by running the oc-mirror command. For example: 

    oc-mirror --config=ImageSetConfiguration.yaml file:///path/to/mirror-archive --authfile /path/to/authfile  --v2
    Note

    The oc-mirror command generates a local workspace containing the mirror archive files and the required cluster manifests.

  3. Transfer the directory specified by /path/to/mirror-archive to a bastion host within your disconnected environment.

  4. From the bastion host which has access to the mirror registry, mirror the images from the disk directory to your target registry. For example: 

    oc-mirror --v2 --from <mirror-archive-file> docker://<target-registry-url:port> --workspace file://<workspace folder> --authfile /path/to/authfile

    where:

    <mirror-archive-file>
    Enter the name of the transferred tar file.
    <target-registry-url:port>
    Enter your local registry, for example, registry.localhost:5000.

  5. Apply the cluster-wide resources generated during the push step to redirect all image pulls to your local registry, as shown in the following example: 

    cd <workspace folder>/working-dir/cluster-resources/
oc apply -f .

  6. Download the Node Package Manager (NPM) packages for orchestrator 1.7.1 using any of the following methods:

  7. Push the NPM packages you have downloaded to your NPM server, as shown in the following example: 

    npm publish backstage-plugin-orchestrator-1.7.1.tgz
npm publish backstage-plugin-orchestrator-backend-dynamic-1.7.1.tgz
npm publish backstage-plugin-orchestrator-form-widgets-1.7.1.tgz
npm publish backstage-plugin-scaffolder-backend-module-orchestrator-dynamic-1.7.1.tgz
  8. Install the OpenShift Serverless Operator and OpenShift Serverless Logic Operators using OperatorHub.
  9. Create a Backstage custom resource (CR).

  10. Configure the Backstage CR for the Orchestrator as described in the Orchestrator plugin dependencies for Operator installation.

    Create all the resources and configure the Backstage instance accordingly. See Configuring a custom NPM registry for instructions on how to point RHDH towards the custom NPM registry.

Verification

  • Restart the RHDH pod and wait for the components to deploy properly.
  • Once stable, go to the RHDH UI, and confirm that the Orchestrator UI is accessible and functioning correctly.
Note

The successful accessibility of the Orchestrator UI confirms that the underlying components are running and the cluster recognizes the plugin.

You can install Red Hat Developer Hub with Orchestrator plugin in a partial air-gapped environment using the Operator.

A disconnected installation prevents unauthorized access, data transfer, or communication with external sources.

You can use the oc-mirror command to mirror resources directly to your accessible local mirror registry and apply the generated cluster resources.

Prerequisites

  • You have mirrored the Red Hat Developer Hub Operator images to the local registry using the RHDH mirroring script. For more information, see Installing Red Hat Developer Hub in a partially disconnected environment with the Operator.
  • You have set up your disconnected environment using a local registry.
  • You have permissions to push NPM packages to an NPM server available in your restricted network.
  • You have installed the oc-mirror tool, with a version corresponding to the version of your OpenShift Container Platform cluster.

Procedure

  1. Create an ImageSetConfiguration file for oc-mirror. You must include the images and operators required by the Serverless Logic Operator in the ImageSetConfiguration file, as oc-mirror does not automatically mirror all images. Use the following example: 

    apiVersion: mirror.openshift.io/v2alpha1
kind: ImageSetConfiguration
mirror:
  additionalimages:
  - name: registry.redhat.io/openshift-serverless-1/logic-jobs-service-postgresql-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-jobs-service-ephemeral-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-data-index-postgresql-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-data-index-ephemeral-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-db-migrator-tool-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-swf-builder-rhel8:1.36.0
  - name: registry.redhat.io/openshift-serverless-1/logic-swf-devmode-rhel8:1.36.0
  operators:
    - catalog: registry.redhat.io/redhat/redhat-operator-index:4.19
      # For example: registry.redhat.io/redhat/redhat-operator-index:v4.19
      packages:
      - name: logic-operator-rhel8
        channels:
        - name: alpha
          minVersion: 1.36.0
          maxVersion: 1.36.0
      - name: serverless-operator
        channels:
        - name: stable
          minVersion: 1.36.0
          maxVersion: 1.36.1

    Alternatively, you can use the podman commands to find the missing images and add them to the additionalimages list if the versions change: 

    IMG=registry.redhat.io/openshift-serverless-1/logic-operator-bundle:1.36.0-8
mkdir local-manifests-osl
podman create --name temp-container "$IMG" -c "cat /manifests/logic-operator-rhel8.clusterserviceversion.yaml"
podman cp temp-container:/manifests ./local-manifests-osl
podman rm temp-container
yq -r '.data."controllers_cfg.yaml" | from_yaml | .. | select(tag == "!!str") | select(test("^.\\/.:.*$"))' ./local-manifests-osl/manifests/logic-operator-rhel8-controllers-config_v1_configmap.yaml

  2. Mirror the images in the ImageSetConfiguration.yaml file by running the oc-mirror command. For example: 

    oc-mirror --config=imagesetconfiguration.yaml docker://<registry URL:port> --workspace file://<workspace folder> --authfile /path/to/authfile  --v2
cd <workspace folder>/working-dir/cluster-resources/
oc apply -f .

  3. Download the Node Package Manager (NPM) packages for orchestrator 1.7.1 using any of the following methods:

  4. Push the NPM packages you have downloaded to your NPM server, as shown in the following example: 

    npm publish backstage-plugin-orchestrator-1.7.1.tgz
npm publish backstage-plugin-orchestrator-backend-dynamic-1.7.1.tgz
npm publish backstage-plugin-orchestrator-form-widgets-1.7.1.tgz
npm publish backstage-plugin-scaffolder-backend-module-orchestrator-dynamic-1.7.1.tgz
  5. Install the OpenShift Serverless Operator and OpenShift Serverless Logic Operators using OperatorHub.
  6. Create a Backstage custom resource (CR).

  7. Configure the Backstage CR for the Orchestrator as described in the Orchestrator plugin dependencies for Operator installation.

    Create all the resources and configure the Backstage instance accordingly. See Configuring a custom NPM registry for instructions on how to point RHDH towards the custom NPM registry.

Verification

  • Restart the RHDH pod and wait for the components to deploy properly.
  • Once stable, go to the RHDH UI, and confirm that the Orchestrator UI is accessible and functioning correctly.
Note

The successful accessibility of the Orchestrator UI confirms that the underlying components are running and the cluster recognizes the plugin.

Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

Legal Notice

Theme

© 2026 Red Hat맨 위로 이동