Avoiding Unexpected Upgrades for IBM Fusion

To avoid this issue and ensure that upgrades are controlled, use the dedicated IBM Fusion catalog that matches your target release version instead of the general ibm-operator-catalog. Using the dedicated catalog helps to maintain version stability and provides predictable upgrade behaviour across your environments.

Resolution:

1. Create and use a dedicated catalog source for the required IBM Fusion version.
   
   For example: 
   
   The catalog created with the name isf-software-catalog for IBM Fusion version 2.11.0
    

   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: isf-software-catalog
     namespace: openshift-marketplace
   spec:
     displayName: Fusion Software Catalogsource
     image: 'icr.io/cpopen/isf-operator-software-catalog:2.11.0'
     publisher: IBM
     sourceType: grpcOnce the CatalogSource shows Ready, update the IBM Fusion operator subscription.

2. Update the IBM Fusion subscription to use this dedicated catalog:

   apiVersion: operators.coreos.com/v1alpha1
   kind: Subscription
   metadata:
     name: isf-operator
     namespace: ibm-spectrum-fusion-ns
   spec:
     channel: v2.0
     installPlanApproval: Automatic
     name: isf-operator
     source: isf-software-catalog        # <-- Update with the Fusion-specific catalog name
     sourceNamespace: openshift-marketplace
     startingCSV: isf-operator.v2.11.0																		

3. To upgrade, navigate to the IBM Fusion operator and check if the Upgrade available option is displayed.
4. Verify that the new catalog is referenced and utilized.
5. Once confirmed, click Upgrade to proceed with the upgrade process.