Based on the Disconnected (Air-gapped) UPI installation process described into Experimental Developer Preview Builds

reference : Preview of Disconnected (Air-gapped) Install & Update Guide

The work is based on this document

$ git clone https://github.com/dwojciec/OLM-disconnected.git

Here is an example about env.sh file that contains information about quay access with your private quay account to push the image created or to access quay with your subscription account

export MIRROR_REGISTRY='Y'
export AIRGAP_REG='bastion.registry.example.com:5000'
export AIRGAP_REPO='ocp4/openshift4'
export QUAY_AUTH_TOKEN=b3BlbnNoaWZ0LXJlbGVhc2UtZGV2K2R3b2pjaWVjcmVkaGF0Y29tMWpjd2VyeGFnc29pbzZuanhid3ZkYXFxbGlqOllGQzNIQ1g4SjlJNlZXUklMVlNCT1U1RjRVVkFGVkM4MTYxMEZCMU5VSlBLVUlCxsxsx
export AIRGAP_SECRET_JSON='pull-secret-3.json'
export QUAY_PRIVATE_JSON='example-auth.json'
export QUAY_USER=dwojciec
export CATALOG_OPERATOR_IMAGE=example-registry

This script is creating the list of packages that are available for the default operators sources. This script is generating a json format file called packages.txt

$ ./retrieve-package-list.sh

This script is creating a Operator Catalog Image with all operators list generated during the previous Retrieve package lists step. This script is running in 4 phases :

• Generate the list of operators into namespaces.txt file to include into the Operator Catalog Image.
• you can update the namespaces.txt file from another Terminal session if you want to remove some operators from the list.
• Optional Pull locally all container images using by Operators list.
• Optional : Tag all container images pulled with the bastion server reference
• Build of the Operator Catalog image container.
• Push the image to your own Quay repository to share it with other people.

$ ./create-operator-catalog-img.sh 

During this process the yaml file catalogsource.yaml is generated. example of this file.

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: example-manifests
  namespace: default
spec:
  sourceType: grpc
  image: <path to the the image>/example-registry:latest

To use the mirrored images you will need to specify an ImageContentSourcePolicy to change the location of the operator image:

Example:

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: example
spec:
  repositoryDigestMirrors:
  - mirrors:
    - <bastion_host_name>:5000/<namespace>/<name>
    source: quay.io/<user or organizations>/<namespace>/<name>

To pull the images that you need, you will need to determine the images defined by the operator that you are expecting, and mirror those images by pulling the images and pushing those images into the bastion_host.

Your new operators should now be available in OperatorHub.

• Operator Registry runs in a Kubernetes or OpenShift cluster to provide operator catalog data to Operator Lifecycle Manager.