Soon, all Red Hat OpenShift documentation will only be available on docs.redhat.com, the official location of all Red Hat product documentation. Get familiar with the updated experience today!
  1. Documentation
×

Uninstalling the Compliance Operator

You can remove the OpenShift Compliance Operator from your cluster by using the OKD web console.

Uninstalling the OpenShift Compliance Operator from OKD

To remove the Compliance Operator, you must first delete the Compliance Operator custom resource definitions (CRDs). After the CRDs are removed, you can then remove the Operator and its namespace by deleting the openshift-compliance project.

Prerequisites

  • Access to an OKD cluster using an account with cluster-admin permissions.

  • The OpenShift Compliance Operator must be installed.

Procedure

To remove the Compliance Operator by using the OKD web console:

  1. Remove CRDs that were installed by the Compliance Operator:

    1. Switch to the Administration → CustomResourceDefinitions page.

    2. Search for compliance.openshift.io in the Name field.

    3. Click the Options menu kebab next to each of the following CRDs, and select Delete Custom Resource Definition:

      • ComplianceCheckResult

      • ComplianceRemediation

      • ComplianceScan

      • ComplianceSuite

      • ProfileBundle

      • Profile

      • Rule

      • ScanSettingBinding

      • ScanSetting

      • TailoredProfile

      • Variable

  2. Remove the OpenShift Compliance project:

    1. Switch to the Home → Projects page.

    2. Click the Options menu kebab next to the openshift-compliance project, and select Delete Project.

    3. Confirm the deletion by typing openshift-compliance in the dialog box, and click Delete.