Uninstalling License Service

Learn how to uninstall License Service from your cluster.

Complete the following procedure to uninstall License Service.

Note: The following procedure assumes that you have deployed IBM License Service in the ibm-common-services namespace.

Before you begin

Before uninstalling License Service, create an audit snapshot to record your license usage until the uninstallation for audit purposes. If you plan to reinstall License Service, the license usage data is stored in the persistent cluster memory and should not be affected by reinstallation. However, it is still a good practice to create an audit snapshot before reinstalling License Service as a precaution.

Uninstallation path is linked to the installation method. The following table shows how to uninstall License Service depending on the deployment scenario that was used for installation.

Uninstallation path	Deployment scenario
Follow uninstallation with Operator Lifecycle Manager (OLM)	Automatic installation using Operator Lifecycle Manager (OLM) Manual installation on OpenShift Container Platform (OCP) version 4.10 or later Manual installation on Kubernetes from scratch with `kubectl`
Follow uninstallation without Operator Lifecycle Manager (OLM)	Offline installation Manual installation without Operator Lifecycle Manager (OLM)

Complete the following steps to uninstall License Service.

Step 1: Deleting the IBM Licensing instance
Step 2: Deleting the remaining License Service resources
- Uninstallation with Operator Lifecycle Manager (OLM)
- Uninstallation without Operator Lifecycle Manager (OLM)
Step 3: Verifying uninstallation
- With Operator Lifecycle Manager (OLM)
- Without Operator Lifecycle Manager (OLM)

Step 1: Deleting the IBM Licensing instance

Delete the IBMLicensing custom resource. Once you delete the instance, the operator will clean its resources.

Check what ibmlicensing instances you have by running the following command:

licensingNamespace=ibm-common-services
kubectl get ibmlicensing -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}"

The command should return one instance.

Delete this instance, if it exists with the following command:

licensingNamespace=ibm-common-services
instanceName=`kubectl get ibmlicensing -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}"`
kubectl delete ibmlicensing ${instanceName} -n ${licensingNamespace}

Step 2: Deleting the remaining License Service resources

Note: The number and type of resources that are created on a cluster depend on a version and License Service installation method. Because of that, some resources that are listed might not be present.

Select the procedure for your environment:

Uninstallation with Operator Lifecycle Manager (OLM)
Uninstallation without Operator Lifecycle Manager (OLM)

Uninstallation with Operator Lifecycle Manager (OLM)

Delete the operator subscription.

Run the following command to see your subscriptions:

licensingNamespace=ibm-common-services
kubectl get subscription -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}"

Delete the ibm-licensing-operator-app subscription by using the following command:

licensingNamespace=ibm-common-services
subName=ibm-licensing-operator-app
kubectl delete subscription ${subName} -n ${licensingNamespace}

Delete Cluster Service Version (CSV).

Delete CSV that manages the Operator image. Run the following command to get your CSV name, look for ibm-licensing-operator:

licensingNamespace=ibm-common-services
kubectl get clusterserviceversion -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}"
kubectl get clusterserviceversion -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}" | grep ibm-licensing-operator

Delete it by using the following command:

licensingNamespace=ibm-common-services
csvName=`kubectl get clusterserviceversion -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}" | grep ibm-licensing-operator`
kubectl delete clusterserviceversion ${csvName} -n ${licensingNamespace}

Delete the Custom Resource Definition (CRD).

Delete the custom resource definition with the following command:

kubectl delete CustomResourceDefinition ibmlicensings.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicenseservicereporters.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingdefinitions.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingmetadatas.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingquerysources.operator.ibm.com

Delete Operator Group.

To check if you have operator group tied to ibm-common-services namespace, run the following command:

kubectl get OperatorGroup -n ibm-common-services

It might display the following:

kubectl get OperatorGroup -n ibm-common-services
# NAME                        AGE
# operatorgroup               24m

Or,

kubectl get OperatorGroup -n ibm-common-services
# NAME                        AGE
# ibm-common-services-82lx5   24m

If IBM Licensing operator was the only one tied to that Operator Group, you can delete that Operator Group by using the following command:

licensingNamespace=ibm-common-services
operatorGroupName=`kubectl get OperatorGroup -n ${licensingNamespace} -o jsonpath="{range .items[*]}{.metadata.name}{'\n'}"`
kubectl delete OperatorGroup ${operatorGroupName} -n ${licensingNamespace}

Delete CatalogSource.

Note: If you have other services that use the opencloudio CatalogSource do not delete it. Otherwise, you can delete the CatalogSource with the following command:

# Make sure GLOBAL_CATALOG_NAMESPACE has global catalog namespace value.
opencloudioSourceName=opencloud-operators
kubectl delete CatalogSource ${opencloudioSourceName} -n ${GLOBAL_CATALOG_NAMESPACE}

Uninstall OLM.

For more information, see Uninstall in OLM documentation.

Uninstallation without Operator Lifecycle Manager (OLM)

Delete the operator deployment by running the following command.

licensingNamespace=ibm-common-services
kubectl delete deployment ibm-licensing-operator -n ${licensingNamespace}

Delete the role-based access control (RBAC) with the following command.

# configure namespace:
licensingNamespace=ibm-common-services
# delete rbac for operand:
kubectl delete RoleBinding ibm-license-service -n ${licensingNamespace}
kubectl delete RoleBinding ibm-license-service-restricted -n ${licensingNamespace}
kubectl delete ClusterRoleBinding ibm-license-service
kubectl delete ClusterRoleBinding ibm-license-service-restricted
kubectl delete ClusterRoleBinding ibm-licensing-default-reader
kubectl delete ServiceAccount ibm-license-service -n ${licensingNamespace}
kubectl delete ServiceAccount ibm-license-service-restricted -n ${licensingNamespace}
kubectl delete ServiceAccount ibm-licensing-default-reader -n ${licensingNamespace}
kubectl delete Role ibm-license-service -n ${licensingNamespace}
kubectl delete Role ibm-license-service-restricted -n ${licensingNamespace}
kubectl delete ClusterRole ibm-license-service
kubectl delete ClusterRole ibm-license-service-restricted
kubectl delete ClusterRole ibm-licensing-default-reader
# delete rbac for operator:
kubectl delete RoleBinding ibm-licensing-operator -n ${licensingNamespace}
kubectl delete ClusterRoleBinding ibm-licensing-operator
kubectl delete ServiceAccount ibm-licensing-operator -n ${licensingNamespace}
kubectl delete Role ibm-licensing-operator -n ${licensingNamespace}
kubectl delete ClusterRole ibm-licensing-operator

Delete the Custom Resource Definition (CRD).

Delete the custom resource definition with the following command:

kubectl delete CustomResourceDefinition ibmlicensings.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicenseservicereporters.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingdefinitions.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingmetadatas.operator.ibm.com
kubectl delete CustomResourceDefinition ibmlicensingquerysources.operator.ibm.com

Remove the remaining License Service elements.

If you pushed the IBM Licensing Docker images to your private registry, delete the images directly from that registry.
Delete the images from the system where you downloaded the IBM Licensing images that you later pushed to your private registry with the following command.

# on machine with access to internet
export my_docker_registry=<YOUR REGISTRY IMAGE PREFIX HERE e.g.: "my.registry:5000" or "quay.io/opencloudio">
export operator_version=$(git describe --tags --abbrev=0 | tr -d v)
export operand_version=$(git describe --tags --abbrev=0 | tr -d v)
# remove images
docker rmi icr.io/cpopen/ibm-licensing-operator:${operator_version}
docker rmi ${my_docker_registry}/ibm-licensing-operator:${operator_version}
docker rmi icr.io/cpopen/cpfs/ibm-licensing:${operand_version}
docker rmi ${my_docker_registry}/ibm-licensing:${operand_version}
# you might want to check if you don't have other images and delete them as well:
docker images | grep ibm-licensing

If you cloned the ibm-licensing-operator repository into your local system, delete it.

Results: License Service offline installation is completely removed and License Service uninstallation is completed.

Step 3: Verifying uninstallation

To verify that License Service is fully uninstalled, complete the following steps:

With Operator Lifecycle Manager (OLM)

Verify whether the License Service Catalog Source is deleted.

Note: If you have other services that use the opencloudio Catalog Source, do not delete it.
```
kubectl get CatalogSource -A | grep opencloud-operators
```
As a response you should get an empty list.
Verify whether the License Service Operator Group is deleted.

Note: If you have other subscriptions that are tied with this Operator Group, do not delete it.
```
licensingNamespace=ibm-common-services
operatorGroupName=operatorgroup
kubectl get OperatorGroup ${operatorGroupName} -n ${licensingNamespace}
```
As a response you should get an empty list.
Verify whether the Custom Resource Definitions (CRDs) are deleted.
```
kubectl get CustomResourceDefinition | grep ibmlicens
```
As a response you should get an empty list.
Verify whether the Cluster Service Versions are deleted.
```
kubectl get clusterserviceversion -A | grep ibm-licensing-operator
```
As a response you should get an empty list.
Verify whether the Subscription is deleted.
```
kubectl get subscription -A | grep ibm-licensing-operator
```
As a response you should get an empty list.

Verify whether role-based access controls (RBAC) are deleted.

kubectl get ClusterRole | grep ibm-licens
kubectl get ClusterRoleBinding | grep ibm-licens
kubectl get Role -A | grep ibm-licens
kubectl get RoleBinding -A | grep ibm-licens
kubectl get ServiceAccount -A | grep ibm-licens

As a response you should get an empty list.

Verify whether License Service deployments are deleted.
```
kubectl get Deployment -A | grep ibm-licens
```
As a response you should get an empty list.

Without Operator Lifecycle Manager (OLM)

Verify whether the Custom Resource Definitions (CRDs) are deleted.
```
kubectl get CustomResourceDefinition | grep ibmlicens
```
As a response you should get an empty list.

Verify whether role-based access controls (RBAC) are deleted.

kubectl get ClusterRole | grep ibm-licens
kubectl get ClusterRoleBinding | grep ibm-licens
kubectl get Role -A | grep ibm-licens
kubectl get RoleBinding -A | grep ibm-licens
kubectl get ServiceAccount -A | grep ibm-licens

As a response you should get an empty list.

Verify whether License Service deployments are deleted.
```
kubectl get Deployment -A | grep ibm-licens
```
As a response you should get an empty list.