File Integrity Operator pod container permissions

sheriff-rh · sheriff-rh · commit 39ac9c65eda9 · 2022-10-28T10:52:49.000-04:00
Peer review feedback
diff --git a/modules/compliance-operator-cli-installation.adoc b/modules/compliance-operator-cli-installation.adoc
@@ -25,7 +25,7 @@ metadata:
     pod-security.kubernetes.io/enforce: privileged <1>
   name: openshift-compliance
 ----
-<1> In {product-title} {product-version} with Compliance Operator version 0.1.53 or later, the pod security label must be set to `privileged` at the namespace level.
+<1> In {product-title} {product-version}, the pod security label must be set to `privileged` at the namespace level.
 
 . Create the `Namespace` object:
 +
diff --git a/modules/file-integrity-operator-installing-cli.adoc b/modules/file-integrity-operator-installing-cli.adoc
@@ -27,8 +27,10 @@ kind: Namespace
 metadata:
   labels:
     openshift.io/cluster-monitoring: "true"
+    pod-security.kubernetes.io/enforce: privileged <1>
   name: openshift-file-integrity
 ----
+<1> In {product-title} {product-version}, the pod security label must be set to `privileged` at the namespace level.
 
 . Create the `OperatorGroup` object YAML file:
 +

Original file line number	Diff line number	Diff line change
`@@ -25,7 +25,7 @@ metadata:`
`25`	`25`	`pod-security.kubernetes.io/enforce: privileged <1>`
`26`	`26`	`name: openshift-compliance`
`27`	`27`	`----`
`28`		-<1> In {product-title} {product-version} with Compliance Operator version 0.1.53 or later, the pod security label must be set to `privileged` at the namespace level.
	`28`	+<1> In {product-title} {product-version}, the pod security label must be set to `privileged` at the namespace level.
`29`	`29`
`30`	`30`	. Create the `Namespace` object:
`31`	`31`	`+`