-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Updating Compliance Operator docs #29673
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Deploy preview for osdocs ready! Built with commit 344aa99 |
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
ab972d0 to
2d22b19
Compare
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
security/compliance_operator/compliance-operator-installation.adoc
Outdated
Show resolved
Hide resolved
2d22b19 to
ff9c0fc
Compare
JAORMX
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice!!
ff9c0fc to
d2a33a4
Compare
|
@pdhamdhe Please provide QE review. Thank you! |
JAORMX
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks great! Just did a small comment and I think this is good to go.
d2a33a4 to
ce8dab1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for the subscription, there is an important field called "channel":
a. Run the following command to set the OpenShift Container Platform major and minor version as an environment variable, which is used as the channel value in the next step.
OC_VERSION=$(oc version -o yaml | grep openshiftVersion | grep -o '[0-9]*[.][0-9]*' | head -1)
b. Create the Subscription object YAML file by running:
----
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: compliance-operator-sub
namespace: openshift-compliance
spec:
channel: "${OC_VERSION}"
installPlanApproval: Automatic
name: compliance-operator
source: redhat-operators
sourceNamespace: openshift-marketplace
----
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good if we mention channel while creating subscription but it is not mandatory. We can create subscription without mentioning channel and operator will get deployed using defaultChannel
$ oc get packagemanifest compliance-operator -oyaml |grep defaultChannel
defaultChannel: "4.6"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pdhamdhe If works for 4.6. What if a 4.7 cluster? It will have 2 packagemanifests(one for 4.6 and the other one for 4.7). If so, for fresh install, it is better to recommend users to use OCP version instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@xiaojiey Jfyi.. By default there will be only one packagemanifest for each ocp version for operator. So on 4.7 cluster, the compliance operator packagemanifest will only have defaultChannel : "4.7" . I was able to installed operator on both the cluster i.e 4.6 & 4.7 using the subscription yaml file which is mentioned in documentation. Though, I am fine with both the methods.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
‘ProfileBundle’ is much reasonable, as it is a CR name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No need to apply the file if we are creating namespace resource using $ oc create -f <file-name>.yaml and step 2 can be merged in step 1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is ScanSetting object. In point 5 & 6, it is mentioned scan setting binding, please make correction.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also ScanSetting runs scans at 01:00 everyday not periodically every hour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be good if we add -n openshift-compliance in all command mentioned in this section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct command would be :
$ oc get compliancecheckresults -l 'compliance.openshift.io/check-status=FAIL,compliance.openshift.io/automated-remmediation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also here, please update the selector to compliance.openshift.io/check-status=FAIL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This reworking of the Compliance Operator section looks great. I left feedback for general guidelines adherence and minimalism/simplification purposes.
It looks like there is a mix of command lead-in sentences (this inconsistency is present through the OCP docs), so I gave some varying feedback depending on the assembly. Examples:
To list all failing checks that can be remediated automatically , run:
Search for any outdated remediations:
Create a namespace object YAML file by running:
For the sake of minimalism, I think the second example above works best.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/Compliance Operator Scans/Compliance Operator scans/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be helpful in this intro sentence to say "Compliance Operator."
s/Before you can use the Operator, you must ensure it is deployed in the cluster./Before you can use the Compliance Operator, you must ensure that it is deployed in the cluster./
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the "not installed successfully" section below, it says to "Navigate to the Operators -> Installed Operators page." Is it important in this first verification step to also include Operators in the navigation directions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be good to specify the "Compliance Operator" here in case there are other Operators installed.
s/the Operator/the Compliance Operator/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/namespace/Namespace/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a Procedure module? If so, you can add .Procedure with a single bullet (or two bullets because this isn't necessarily a sequence).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this a Procedure or Concept module? If Procedure, you can add .Procedure and then have bullets for each potential check? If Concept, I think the rest of the module looks okay as is, but you could change the title to something like "Filters for failed compliance check results".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/To list checks that belong to a specific suite, run:/List checks that belong to a specific suite:/
Similar rewording suggestion applies to the other commands in this module (for minimalism and consistency across the Compliance Operator book).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be a good candidate to split the command into two lines with \.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Might be a good candidate to split the command into two lines with \.
874812b to
25ea12b
Compare
25ea12b to
344aa99
Compare
|
/cherrypick enterprise-4.6 |
|
/cherrypick enterprise-4.7 |
|
/cherrypick enterprise-4.8 |
|
@ahardin-rh: new pull request created: #31436 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@ahardin-rh: new pull request created: #31437 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@ahardin-rh: new pull request created: #31438 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Preview Build: https://deploy-preview-29673--osdocs.netlify.app/openshift-enterprise/latest/security/compliance_operator/compliance-operator-installation.html
Addresses: