Skip to content

Commit 7c301bd

Browse files
committed
OSDOCS-2656: Adding section about Uninstalling the Compliance Operator
1 parent 9079285 commit 7c301bd

File tree

3 files changed

+60
-0
lines changed

3 files changed

+60
-0
lines changed

_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -786,6 +786,8 @@ Topics:
786786
File: compliance-operator-advanced
787787
- Name: Troubleshooting the Compliance Operator
788788
File: compliance-operator-troubleshooting
789+
- Name: Uninstalling the Compliance Operator
790+
File: compliance-operator-uninstallation
789791
- Name: Using the oc-compliance plug-in
790792
File: oc-compliance-plug-in-using
791793
- Name: File Integrity Operator
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
// Module included in the following assemblies:
2+
//
3+
// security/compliance_operator/compliance-operator-uninstallation.adoc
4+
5+
[id="compliance-operator-uninstall_{context}"]
6+
= Uninstalling the OpenShift Compliance Operator from {product-title}
7+
8+
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.
9+
10+
.Prerequisites
11+
12+
* Access to an {product-title} cluster using an account with `cluster-admin` permissions.
13+
* The OpenShift Compliance Operator must be installed.
14+
15+
.Procedure
16+
17+
To remove the Compliance Operator by using the {product-title} web console:
18+
19+
. Remove CRDs that were installed by the Compliance Operator:
20+
21+
.. Switch to the *Administration* -> *CustomResourceDefinitions* page.
22+
23+
.. Search for `compliance.openshift.io` in the *Name* field.
24+
25+
.. Click the Options menu {kebab} next to each of the following CRDs, and select *Delete Custom Resource Definition*:
26+
27+
* `ComplianceCheckResult`
28+
* `ComplianceRemediation`
29+
* `ComplianceScan`
30+
* `ComplianceSuite`
31+
* `ProfileBundle`
32+
* `Profile`
33+
* `Rule`
34+
* `ScanSettingBinding`
35+
* `ScanSetting`
36+
* `TailoredProfile`
37+
* `Variable`
38+
+
39+
. Remove the OpenShift Compliance project:
40+
41+
.. Switch to the *Home* -> *Projects* page.
42+
43+
.. Click the Options menu {kebab} next to the *openshift-compliance* project, and select *Delete Project*.
44+
45+
.. Confirm the deletion by typing `openshift-compliance` in the dialog box, and click *Delete*.
46+
47+
48+
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
[id="compliance-operator-uninstallation_{context}"]
2+
= Uninstalling the Compliance Operator
3+
include::modules/common-attributes.adoc[]
4+
:context: compliance-operator-uninstallation
5+
6+
toc::[]
7+
8+
You can remove the OpenShift Compliance Operator from your cluster by using the {product-title} web console.
9+
10+
include::modules/compliance-operator-uninstall.adoc[leveloffset=+1]

0 commit comments

Comments
 (0)