Bug 1975784, added oc-compliance plug-in installation procedure

Author: ahardin-rh

modules/oc-compliance-installing.adoc

@@ -0,0 +1,24 @@
+// Module included in the following assemblies:
+//
+// * security/oc_compliance_plug_in/oc-compliance-plug-in-using.adoc
+
+[id="installing-oc-compliance_{context}"]
+= Installing the oc-compliance plug-in
+
+.Procedure
+
+. Extract the `oc-compliance` image to get the `oc-compliance` binary:
++
+[source,terminal]
+----
+$ podman run --rm --entrypoint /bin/cat registry.redhat.io/compliance/oc-compliance-rhel8 /usr/bin/oc-compliance > ~/.local/bin/oc-compliance
+----
++
+.Example output
++
+[source,terminal]
+----
+W0611 20:35:46.486903   11354 manifest.go:440] Chose linux/amd64 manifest from the manifest list.
+----
++
+You can now run `oc-compliance`.

security/oc_compliance_plug_in/oc-compliance-plug-in-using.adoc

@@ -8,6 +8,8 @@ toc::[]
 Although the xref:../../security/compliance_operator/compliance-operator-understanding.adoc#understanding-compliance-operator[Compliance Operator] automates many of the checks and remediations for the cluster, the full process of bringing a cluster into compliance often requires administrator interaction with the Compliance Operator API and other components. The `oc-compliance` plug-in makes the process easier.
 
 
+include::modules/oc-compliance-installing.adoc[leveloffset=+1]
+
 include::modules/oc-compliance-fetching-raw-results.adoc[leveloffset=+1]
 
 include::modules/oc-compliance-rerunning-scans.adoc[leveloffset=+1]