Enable Operator for restricted network (air-gapped or proxied) environments

[rm3l]

As an administrator, I want to run the Operator in a restricted network, or disconnected, environment, So that users can have a fully functional Backstage instance running under such restricted environments.

See https://docs.openshift.com/container-platform/4.14/operators/operator_sdk/osdk-generating-csvs.html#olm-enabling-operator-for-restricted-network_osdk-generating-csvs

See also https://issues.redhat.com/browse/RHIDP-488

[nickboldt]

Testing required:

• install with operator
• install with operator using postgres; verify the postgres pod starts and can be used

---

Pseudo-code for a test:

• start a cluster
• mirror images in the CSV to that cluster according to https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.10/html-single/administration_guide/index#installing-devspaces-in-a-restricted-environment or https://docs.openshift.com/container-platform/4.13/installing/disconnected_install/installing-mirroring-installation-images.html
• add catalog source for the operator subscription
• "turn off the internet" via whatever proxy or DNS config works for you
• perform operator install
• verify pods all start (including postgres and dev hub)
• verify RHDH loads (route works)

[gazarenkov]

As discussed, manual testing with CSV and Airgapped environment part of Admin doc are parts of DoD.

[rm3l]

As discussed, manual testing with SCV and Airgapped environment part of Admin doc are parts of DoD.

I've added this point to the documentation issue: #28