Cleaning existing License Service dependencies - outside of OpenShift and on OpenShift Container Platform

Earlier versions of License Service, up to 1.1.3, used OperatorSource and Operator Marketplace. These dependencies are no longer needed. If you installed the earlier version of License Service, before installing the new version remove the existing dependencies from your system.

Cleaning existing License Service dependencies outside of OpenShift

1. Delete OperatorSource.

   To delete an existing OpenSource, run the following command:

   GLOBAL_CATALOG_NAMESPACE=olm
   opencloudioSourceName=opencloud-operators
   kubectl delete OperatorSource ${opencloudioSourceName} -n ${GLOBAL_CATALOG_NAMESPACE}
   

   where GLOBAL_CATALOG_NAMESPACE value is your global catalog namespace.

2. Delete OperatorMarketplace.

   Note: Before deleting OperatorMarketplace check whether it is not used elsewhere, for example, for other Operators from OperatorMarketplace.

   To delete OperatorMarketplace, run the following command:

   GLOBAL_CATALOG_NAMESPACE=olm
   kubectl delete Deployment marketplace-operator -n ${GLOBAL_CATALOG_NAMESPACE}
   kubectl delete RoleBinding marketplace-operator -n ${GLOBAL_CATALOG_NAMESPACE}
   kubectl delete ClusterRoleBinding marketplace-operator
   kubectl delete ServiceAccount marketplace-operator -n ${GLOBAL_CATALOG_NAMESPACE}
   kubectl delete Role marketplace-operator -n ${GLOBAL_CATALOG_NAMESPACE}
   kubectl delete ClusterRole marketplace-operator
   

   where GLOBAL_CATALOG_NAMESPACE value is your global catalog namespace.

3. Reinstall License Service to get CatalogSource that is missing. For more information, see Installing License Service.

Cleaning existing License Service dependencies on OpenShift Container Platform

1. Delete OperatorSource.

   To delete an existing OpenSource, run the following command:

   GLOBAL_CATALOG_NAMESPACE= openshift-marketplaceolm
   opencloudioSourceName=opencloud-operators
   kubectl delete OperatorSource ${opencloudioSourceName} -n ${GLOBAL_CATALOG_NAMESPACE}
   

2. Reinstall License Service to get CatalogSource that is missing. For more information, see Installing License Service.

Modifying the application deployment resources

You can modify the resources that are requested and limited by the Deployment for Application by editing the IBMLicensing instance.

To learn what resources are required for License Service in your environment, see Supported platforms and hardware requirements: Required resources.

1. To modify the IBMLicensing instance, run the following command:

   kubectl edit IBMLicensing instance
   

2. Modify the resource limits and resources in the following yaml and paste it in the command line.

   apiVersion: operator.ibm.com/v1alpha1
   kind: IBMLicensing
   metadata:
     name: instance
   spec:
   # ...
     resources:
       limits:
         cpu: 500m # <- set the CPU limit to the desired value
         memory: 512Mi # <- set the memory limit to the desired value
       requests:
         cpu: 200m # <- set the requests limit to the desired value
         memory: 256Mi # <- set the memory limit to the desired value
   # ...
   

   Where m stands for Millicores, and Mi for Mebibytes