Chapter 9. Postinstallation configuration for a disconnected IBM Cloud cluster

Procedure

• Disable the sources for the default catalogs by adding disableAllDefaultSources: true to the OperatorHub object:

  $ oc patch OperatorHub cluster --type json \
      -p '[{"op": "add", "path": "/spec/disableAllDefaultSources", "value": true}]'

  Tip

  Or, you can use the web console to manage catalog sources. From the Administration Cluster Settings Configuration OperatorHub page, click the Sources tab, where you can create, update, delete, disable, and enable individual sources.

• The ImageContentSourcePolicy resource associates the mirror registry with the source registry and redirects image pull requests from the online registries to the mirror registry.

• The CatalogSource resource is used by Operator Lifecycle Manager (OLM) Classic to retrieve information about the available Operators in the mirror registry, which lets users discover and install Operators.

  Note

  OLM v1 uses the ClusterCatalog resource to retrieve information about the available cluster extensions in the mirror registry.

  The oc-mirror plugin v1 does not generate ClusterCatalog resources automatically; you must manually create them. The oc-mirror plugin v2 does, however, generate ClusterCatalog resources automatically.

  For more information on creating and applying ClusterCatalog resources, see "Adding a catalog to a cluster" in "Extensions".

Prerequisites

• You have mirrored the image set to the registry mirror in the disconnected environment.
• You have access to the cluster as a user with the cluster-admin role.