RHIDP-8711: Orchestrator flavors airgap support (Helm and Operator)

assemblies/assembly-install-rhdh-orchestrator-plugin-in-an-air-gapped-environment.adoc

@@ -0,0 +1,10 @@
+:_mod-docs-content-type: ASSEMBLY
+
+[id="assembly-install-rhdh-orchestrator-plugin-in-an-air-gapped-environment_{context}"]
+= Installing Orchestrator plugin in an air-gapped environment
+
+You can configure {product} ({product-very-short}) with Orchestrator plugin in an air-gapped environment by using either the Operator or Helm chart.
+
+include::modules/orchestrator/proc-install-rhdh-orchestrator-airgapped-env-using-operator.adoc[leveloffset=+1]
+
+include::modules/orchestrator/proc-install-rhdh-orchestrator-airgapped-env-using-helm-chart.adoc[leveloffset=+1]

modules/orchestrator/proc-install-rhdh-orchestrator-airgapped-env-using-helm-chart.adoc

@@ -0,0 +1,54 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="proc-install-rhdh-orchestrator-airgapped-env-using-helm-chart.adoc_{context}"]
+= Installing {product} with Orchestrator in an air-gapped {ocp-short} environment using the Helm chart
+
+
+.Prerequisites
+
+include::snip-installing-the-orchestrator-common-prerequisites.adoc[]
+
+.Procedure
+
+. Mirror the {product} {product-version} Helm chart images to the local registry. See {installing-in-air-gap-book-link}#assembly-install-rhdh-airgapped-environment-ocp-helm_title-install-rhdh-air-grapped[Installing {product} on {ocp-short} in an air-gapped environment with the Helm chart] for instructions.
+
+. Mirror the `redhat-developer-hub-orchestrator-infra` chart images to the local registry.
+
+include::snip-installing-the-orchestrator-common-steps.adoc[]
+
+. Apply the `redhat-developer-hub-orchestrator-infra` Helm chart and approve the install plans. See {installing-in-air-gap-book-link}#assembly-install-rhdh-airgapped-environment-ocp-helm_title-install-rhdh-air-grapped[Air-gapped installation with Helm chart instructions] for details.
+
+. Apply the {product-very-short} {product-version} Helm chart. Include the version {product-bundle-version} and enable the Orchestrator plugin as shown in the following example:
++
+[source,yaml]
+----
+orchestrator.enabled=true
+----
+
+. The {product-very-short} {product-version} Helm chart defaults to pulling Orchestrator plugins from the official {company-name} NPM registry using full URL references. You must override this behavior to point to your local registry.
++
+To configure the Orchestrator plugins to use a custom registry, complete the following steps:
++
+* Open your `values.yaml` file.
++
+* Explicitly list the Orchestrator plugin packages under the `orchestrator.plugins` section.
+You must replace the full URLs with the simplified package references that point to your custom NPM registry as shown in the following example:
++
+[source,yaml]
+----
+- package: "@redhat/backstage-plugin-orchestrator@{product-bundle-version}"
+- package: "@redhat/backstage-plugin-orchestrator-backend-dynamic@{product-bundle-version}"
+- package: "@redhat/backstage-plugin-scaffolder-backend-module-orchestrator-dynamic@{product-bundle-version}"
+- package: "@redhat/backstage-plugin-orchestrator-form-widgets@{product-bundle-version}"
+----
+
+.Verification
+
+* Restart the {product-very-short} pod and wait for the components to deploy properly.
+
+* After deployment is complete, go to the **{product-very-short}** 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.
+====

modules/orchestrator/proc-install-rhdh-orchestrator-airgapped-env-using-operator.adoc

@@ -0,0 +1,37 @@
+:_mod-docs-content-type: PROCEDURE
+
+[id="proc-install-rhdh-orchestrator-airgapped-env-using-operator.adoc_{context}"]
+= Installing {product} with Orchestrator in an air-gapped {ocp-short} environment using the Operator
+
+You can install {product} with Orchestrator plugin in an air-gapped environment using Operator.
+
+In a network-restricted environment, a disconnected installation prevents unauthorized access, data transfer, or communication with external sources.
+
+.Prerequisites
+
+* You have mirrored the {product} Operator images to the local registry using the included script. For {product-very-short} installation using Operator, the mirroring script automatically deploys the {product-very-short} Operator for you.
+
+include::snip-installing-the-orchestrator-common-prerequisites.adoc[]
+
+.Procedure
+
+include::snip-installing-the-orchestrator-common-steps.adoc[]
+
+. Install the OpenShift Serverless Operator and OpenShift Serverless Logic Operators using the OperatorHub.
+
+. Create a {product-custom-resource-type} custom resource (CR).
+
+. Configure the {product-custom-resource-type} CR for the Orchestrator as described in the {orchestrator-book-link}#con-orchestrator-plugin-dependencies-operator.adoc_orchestrator-rhdh[Orchestrator plugin dependencies for Operator installation].
++
+Create all the resources and configure the {product-custom-resource-type} instance accordingly. See {release-notes-book-link}#removed-functionality-rhdhbugs-2000[Configuring a custom NPM registry] for instructions on how to point {product-very-short} towards the custom NPM registry.
+
+.Verification
+
+* Restart the {product-very-short} pod and wait for the components to deploy properly.
+
+* Once stable, go to the {product-very-short} 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.
+====

modules/orchestrator/snip-installing-the-orchestrator-common-prerequisites.adoc

@@ -0,0 +1,5 @@
+* You have set up your disconnected environment using a local registry.
+
+* You have permissions to push NPM packages to a local NPM server.
+
+* Optional: Create and configure a local NPM server.