A guide to uninstalling the DataPower Operator.

Order of uninstallation

The uninstall steps vary depending on what resources you wish to uninstall.

Uninstalling only the operator

It is possible, and supported, to uninstall the operator leaving behind operands (DataPowerService custom resources, etc.) in a running state. This is often a useful step when troubleshooting operator installation issues.

If you wish to only uninstall the operator, complete the respective uninstall steps below based on your install method.

Uninstalling the operator and operands

If you want to completely remove all DataPower Operator resources and related artifacts from your cluster, complete the respective uninstall steps below based on your install method, and then also remove (delete) the CRDs from the cluster.

Deleting the CRDs from the cluster will remove all operand instances, as well as the operator's conversion webhook Deployment.

Uninstalling with OLM

In the GUI

In the OCP GUI, navigate to Operators->Installed Operators on the left side pane. In the Project dropdown box, select the namespace from which to uninstall. Find the specific DataPower Operator Subscription you wish to uninstall and click the options menu on the right side of the row. Select "Uninstall Operator".

In the CLI

Using the oc CLI tool, delete the DataPower Operator Subscription by doing

oc -n mynamespace delete subscription datapower-operator

Uninstalling with CASE

For uninstalling via CASE, refer to the relevant uninstall command in the CASE document.

Removing CRDs

NOTE: Removing these CRDs will delete ALL respective custom resource instances you have deployed on your cluster; proceed with caution.

To remove the DataPower CRDs from the cluster, run:

kubectl delete crds datapowerservices.datapower.ibm.com
kubectl delete crds datapowermonitors.datapower.ibm.com
kubectl delete crds datapowerrollouts.datapower.ibm.com
kubectl delete crds datapowerservicebindings.datapower.ibm.com