-
Bug
-
Resolution: Done
-
Minor
-
4.12.0
-
None
-
None
-
3
-
False
-
Description of problem:
Compliance Operator profiles don't differentiate application/operating system profiles in the docs I was asked this question via a colleague (and had this question at one point myself): What's the difference between profiles with -node and without? I answered it this way... If you see no `-node` on the profile name, it's focus is on the Kubernetes and OpenShift platform. If you see `-node` on the profile name, it's focus is on the Operating System. Per discussion with Andrew - I have opened this bug for further discussion with the ISC team.
Version-Release number of selected component (if applicable):
4.8 to 4.12
How reproducible:
In docs
Steps to Reproduce:
1. Navigate to https://docs.openshift.com/container-platform/4.12/security/compliance_operator/compliance-operator-supported-profiles.html 2. Look at the profiles
Actual results:
You don't see the definition
Expected results:
Clarity for customers using the profile
Additional info:
Discussed with Andrew/Docs Lead
- links to