cloud-native-postgresql is installed with certified-operators CatalogSource

Symptom

When we check the subscription of the cloud-native-postgresql, we can see it is using the certified-operators catalogsource.

oc get sub cloud-native-postgresql -n <your-foundational-services-namespace>

Cause

IBM CatalogSource that provides cloud-native-postgresql (like cloud-native-postgresql-catalog or ibm-operator-catalog) is unavailable before the ibm-common-service-operator installation.

Solution

1. Deploy the CatalogSource, which provides cloud-native-postgresql.

2. Refresh common-service OperandRegistry:

oc delete opreg common-service -n <your-foundational-services-namespace>
oc delete po -l name=ibm-common-service-operator -n <your-foundational-services-namespace>

If your IBM Cloud Pak is installed in the cluster scope, you must refresh the ibm-common-service-operator in the openshift-operators namespace.

oc delete opreg common-service -n <your-foundational-services-namespace>
oc delete po -l name=ibm-common-service-operator -n openshift-operators

1. Reinstall cloud-native-postgresql operator.

   1. Delete the subscription and the CSV of the cloud-native-postgresql operator.

   2. Restart the ODLM pod:

        oc delete po -l name=operand-deployment-lifecycle-manager -n <your-foundational-services-namespace>