Skip to content

Commit 009fb60

Browse files
committed
Expand CO docs to not claim compliance based on usage
Even though the Compliance Operator comes with multiple profiles, usage of these profiles alone doesn't automatically imply compliance with a particular profile. This can be confusing to readers, and we can clarify that expectation by highlighting it in the supported profiles documentation.
1 parent eb08487 commit 009fb60

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

security/compliance_operator/compliance-operator-supported-profiles.adoc

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,8 @@
44
include::_attributes/common-attributes.adoc[]
55
:context: compliance-operator-supported-profiles
66

7-
There are several profiles available as part of the Compliance Operator (CO) installation.
7+
There are several profiles available as part of the Compliance Operator (CO) installation. While you can use the following profiles to assess gaps in a cluster, usage alone does not infer or guarantee compliance with a particular profile.
8+
89

910
[IMPORTANT]
1011
====

0 commit comments

Comments
 (0)