Chapter 2. Uninstalling OpenShift Pipelines
Cluster administrators can uninstall the Red Hat OpenShift Pipelines Operator by performing the following steps:
Delete the custom resource (CR) for the optional
TektonResultcomponent, if this CR exists, and then delete theTektonConfigCR.ImportantIf you uninstall the Operator without removing the CR of the optional component, you cannot remove the component later.
- Uninstall the Red Hat OpenShift Pipelines Operator.
-
Delete the custom resource definitions (CRDs) of the
operator.tekton.devgroup.
Uninstalling only the Operator will not remove the Red Hat OpenShift Pipelines components created by default when you install the Operator.
2.1. Deleting the OpenShift Pipelines custom resources Copy linkLink copied to clipboard!
You can remove the OpenShift Pipelines custom resources (CRs) to clean up the configuration before uninstalling the Operator. This involves deleting the optional TektonResult component, followed by the main TektonConfig CR.
Procedure
-
In the Administrator perspective of the web console, navigate to Administration
CustomResourceDefinitions. -
Type
TektonResultin the Filter by name field to search for theTektonResultcustom resource definition (CRD). -
Click the name of the
TektonResultCRD to display the details page for the CRD. -
Click the
Instancestab. -
If an instance appears, click the Options menu
for the displayed instance.
-
Select Delete
TektonResult. - Click Delete to confirm the deletion of the CR.
Repeat these steps, searching for
TektonConfigin the Filter by name field. If any instances of this custom resource definition (CRD) exist, delete them.NoteDeleting the CRs also deletes the Red Hat OpenShift Pipelines components and all the tasks and pipelines on the cluster.
ImportantIf you uninstall the Operator without removing the
TektonResultCR, you cannot remove the Tekton Results component later.
2.2. Uninstalling the Red Hat OpenShift Pipelines Operator Copy linkLink copied to clipboard!
You can uninstall the Red Hat OpenShift Pipelines Operator by using the OpenShift Container Platform web console to remove the OpenShift Pipelines service from your cluster. This process involves deleting the Operator subscription and its associated operand instances.
Procedure
-
From the Operators
OperatorHub page, use the Filter by keyword box to search for the Red Hat OpenShift Pipelines Operator. - Click the Red Hat OpenShift Pipelines Operator tile. The Operator tile indicates the installation status.
- In the Red Hat OpenShift Pipelines Operator description page, click Uninstall.
In the Uninstall Operator? window, select Delete all operand instances for this operator, and then click Uninstall.
WarningWhen you uninstall the OpenShift Pipelines Operator, the uninstallation process deletes all resources within the
openshift-pipelinestarget namespace where OpenShift Pipelines is installed, including the secrets you configured.
2.3. Deleting the custom resource definitions of the operator.tekton.dev group Copy linkLink copied to clipboard!
You can delete the operator.tekton.dev custom resource definitions (CRDs) to fully remove all OpenShift Pipelines traces from your cluster. This step ensures that no residual definitions remain after the Operator uninstallation.
Delete the CustomResourceDefinitions of the operator.tekton.dev group. The Red Hat OpenShift Pipelines Operator creates these CRDs by default during installation.
Procedure
-
In the Administrator perspective of the web console, navigate to Administration
CustomResourceDefinitions. -
Type
operator.tekton.devin the Filter by name box to search for the CRDs in theoperator.tekton.devgroup. To delete each of the displayed CRDs, complete the following steps:
-
Click the Options menu
.
-
Select Delete
CustomResourceDefinition. - Click Delete to confirm the deletion of the custom resource definition (CRD).
-
Click the Options menu