5.4 Update the cluster

Inspect cluster resources¶

From your oc mirror command, you could have the following files in your working-dir i.e. /opt/4.17-mirrordata/working-dir/cluster-resources/. It all depends on what you mirrored.

idms-oc-mirror.yaml: This is a list of mappings between the original public registry and your local registry for all images that are identified by their digest (ImageDigestMirrorSet).
itms-oc-mirror.yaml: This is a list of mappings between the original public registry and your local registry for all images that are identified by their tag (ImageTagMirrorSet).

cs-redhat-operator-index-v4-17.yaml/cc-redhat-operator-index-v4-17.yaml: This is the CatalogSource/ClusterCatalog for RedHat Operators.

Important!

Change the name the cs-redhat-operator-index-v4-17.yaml/cc-redhat-operator-index-v4-17.yaml catalog source in the YAML file to redhat-operators as some operators are hardcoded reference this exact catalog source name. Examples below with the highlighted value:

Tip

Use a quick sed command to set the name in both files

sed -i 's/name: cs-redhat-operator-index-v4-17/name: redhat-operators/' /opt/4.17-mirrordata/working-dir/cluster-resources/cs-redhat-operator-index-v4-17.yaml
sed -i 's/name: cc-redhat-operator-index-v4-17/name: redhat-operators/' /opt/4.17-mirrordata/working-dir/cluster-resources/cc-redhat-operator-index-v4-17.yaml

Example: cs-redhat-operator-index-v4-17.yaml

apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: redhat-operators
  namespace: openshift-marketplace
spec:
  image: registry.example.com:8443/ocp/redhat/redhat-operator-index:v4.17
  sourceType: grpc
status: {}

Example: cc-redhat-operator-index-v4-19.yaml

apiVersion: olm.operatorframework.io/v1
kind: ClusterCatalog
metadata:
  annotations:
    createdAt: Monday, 21-Jul-25 21:13:27 UTC
    createdBy: oc-mirror v2
    oc-mirror_version: 4.19.0-202507081507.p0.gf364aec.assembly.stream.el9-f364aec
  name: redhat-operators
spec:
  priority: 0
  source:
    image:
      ref: registry.example.com:8443/ocp/redhat/redhat-operator-index:v4.19
    type: Image
status: {}

cs-certified-operator-index-v4-17.yaml: This is the catalog for operators certified by Red Hat but not necessarily developed by Red Hat.
cs-community-operator-index-v4-17.yaml: This is the catalog source for all community based operators.

Apply the cluster resources¶

Red Hat Docs

If you have OSUS configured, when you apply the newly updates resources the cluster will pick up on the new images and be ready for the updates.

Apply the cluster recources generated by the oc-mirror plugin. This will make your cluster aware of the catalog resources we mirrored earlier so you can utilze OperatorHub to install operators. This will overwrite the resources you applied early when installing the cluster.

oc apply -f /opt/4.17-mirrordata/working-dir/cluster-resources/

Example Output

catalogsource.operators.coreos.com/cs-certified-operator-index-v4-17 created
catalogsource.operators.coreos.com/cs-community-operator-index-v4-17 created
catalogsource.operators.coreos.com/redhat-operators created
imagedigestmirrorset.config.openshift.io/idms-release-0 created
imagedigestmirrorset.config.openshift.io/idms-operator-0 created
imagetagmirrorset.config.openshift.io/itms-release-0 created
imagetagmirrorset.config.openshift.io/itms-generic-0 created
configmap/mirrored-release-signatures created

If you mirrored release images, apply the release image signatures

oc apply -f /opt/4.17-mirrordata/cluster-resources/signature-configmap.json

Your cluster should now be ready to be updated via WebUI or CLI.