Uninstalling from the OCP console

You can uninstall FNCMCluster resources and components from your platform deployment from the OpenShift Container Platform console.

About this task

If you installed the FileNet, to create an FNCMCluster then you can use the OpenShift Container Platform user interface to uninstall it. Uninstalling and cleaning up the cluster involves several separate high-level tasks.

  • Uninstalling the FileNet deployment.
  • Uninstalling the operators.
  • Deleting PVCs and PVs not containing data.
  • Deleting secrets.
  • Deleting the FileNet project or namespace.

To uninstall the FileNet deployment, use the following steps.

Procedure

  1. Log in to your OpenShift Container Platform or ROKS cluster.
  2. Click Administration > Namespaces, and click the namespace that you used to install the FileNet deployment.
  3. Click Operators > Installed Operators, and then click the FNCM Deployment tab.

    The name of the deployment is shown in the list of FNCMClusters.

  4. To the right of the FNCMCluster name, click Delete FNCMCluster.

    The action deletes the resources and the instance is no longer seen in the FNCMCluster list.

    Wait for all the pods in the FileNet namespace to be terminated, except the operator pods, before you go to the next step.

  5. Optional: If you want to uninstall the IBM FileNet Content Manager operator as well, then click Operators > Installed Operators. To the right of the IBM FileNet Content Manager operator, click Uninstall Operator.

    The action deletes the operator and the instance is no longer seen in the Installed Operators list.

    Note: Deleting the FNCMCluster and uninstalling the FNCM operator does not delete the existing PVs/PVC, or the databases that are used by the various components. Check the persisted data before you delete the PVs/PVCs manually to make sure you no longer want to keep them. Likewise, if the data no longer needs to be retained or reused you can delete the databases.

What to do next

If you now plan to install another instance of the FNCM operator, check if the dependencies like Namespaces and OperandRequests are properly deleted.

If you do not plan to install another instance of the FileNet Content Manager, proceed with the steps to clean up the FileNet Content Manager data. For more information about cleaning up your data, see the topic Cleaning up FileNet Content Manager.