OSDOCS-13641: Compliance Operator 1.7.0 release notes

[GroceryBoyJr]

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-13641

Link to docs preview for the 1.7.0 release notes: https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/compliance-operator-release-notes.html

Statement about mixed arches at the top of the installation guide:
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-scans/compliance-scans.html

Supported Compliance Operator Scans: Added CIS 1.7.0 for both NODE and PLATFORM:
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-scans/compliance-operator-supported-profiles.html

Fixed typo. Only one letter changed in the word "Persistent":
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-management/compliance-operator-installation.html

Added link for ScanSetting Custom Resource:
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-scans/compliance-scans.html

QE review:

• QE has approved this change.

NOTE TO REVIEWERS: This PR is for release notes for Compliance Operator 1.7.0. This is an asynchronous release which updates release notes for all of OCP Docs 4.12+ with the updates provided in this release of the Compliance Operator. There are also associated documentation changes for all the new features brought in by this release. Those changes are all the extra previews. They are all small changes, but enough of them pushed the release note to a size "L".

Link to errata for reference: https://errata.devel.redhat.com/advisory/147955

[openshift-ci-robot]

@GroceryBoyJr: This pull request references OSDOCS-13641 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-13641

Link to docs preview:

QE review:

• QE has approved this change.

Additional information: Release notes for Compliance Operator 1.7.0. This is an asynchronous release which updates release notes for all of OCP Docs 4.12+ with the updates provided in this release of the Compliance Operator.

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 openshift-eng/jira-lifecycle-plugin repository.

[ocpdocs-previewbot]

🤖 Mon Apr 28 18:58:38 - Prow CI generated the docs preview:

https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-management/compliance-operator-installation.html
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/compliance-operator-release-notes.html
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-scans/compliance-operator-supported-profiles.html
https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/co-scans/compliance-scans.html

[openshift-ci-robot]

@GroceryBoyJr: This pull request references OSDOCS-13641 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-13641

Link to docs preview: https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/compliance-operator-release-notes.html

QE review:

• QE has approved this change.

Additional information: Release notes for Compliance Operator 1.7.0. This is an asynchronous release which updates release notes for all of OCP Docs 4.12+ with the updates provided in this release of the Compliance Operator.

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 openshift-eng/jira-lifecycle-plugin repository.

[GroceryBoyJr]

@xiaojiey PTAL

[GroceryBoyJr]

@rhmdnd PTAL

[GroceryBoyJr]

@Vincent056 PTAL

[GroceryBoyJr]

/assign @Vincent056
/assign @rhmdnd
/assign @xiaojiey

[openshift-ci-robot]

@GroceryBoyJr: This pull request references OSDOCS-13641 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OSDOCS-13641

Link to docs preview: https://92420--ocpdocs-pr.netlify.app/openshift-enterprise/latest/security/compliance_operator/compliance-operator-release-notes.html

QE review:

• QE has approved this change.

Additional information: Release notes for Compliance Operator 1.7.0. This is an asynchronous release which updates release notes for all of OCP Docs 4.12+ with the updates provided in this release of the Compliance Operator. Link to errata for reference: https://errata.devel.redhat.com/advisory/147955

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 openshift-eng/jira-lifecycle-plugin repository.

[stevsmit]

/cherry-pick enterprise-4.19

[stevsmit]

/cherry-pick enterprise-4.18

[stevsmit]

/cherry-pick enterprise-4.17

[stevsmit]

/cherry-pick enterprise-4.16

[stevsmit]

/cherry-pick enterprise-4.15

[stevsmit]

/cherry-pick enterprise-4.14

[stevsmit]

/cherry-pick enterprise-4.13

[stevsmit]

/cherry-pick enterprise-4.12

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92697

Details

In response to this:

/cherry-pick enterprise-4.19

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92698

Details

In response to this:

/cherry-pick enterprise-4.18

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92699

Details

In response to this:

/cherry-pick enterprise-4.17

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92700

Details

In response to this:

/cherry-pick enterprise-4.16

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92701

Details

In response to this:

/cherry-pick enterprise-4.15

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: new pull request created: #92702

Details

In response to this:

/cherry-pick enterprise-4.14

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: #92420 failed to apply on top of branch "enterprise-4.13":

Applying: OSDOCS-13641: Compliance Operator 1.7.0 release
.git/rebase-apply/patch:18: trailing whitespace.
Increasing the memory limit for the Compliance Operator or the scanner pods is needed if the default limits are not sufficient and the Operator or scanner pods are ended by the Out Of Memory (OOM) process. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/security_and_compliance/compliance-operator#compliance-increasing-operator-limits_compliance-troubleshooting[Increasing Compliance Operator resource limits]. 
.git/rebase-apply/patch:89: trailing whitespace.
BSI (Bundesamt für Sicherheit in der Informationstechnik, Germany’s Federal Office for Information Security) compliance is legally mandated under Germany’s IT Security Act (IT-Sicherheitsgesetz) for critical infrastructure sectors like energy, healthcare, and telecommunications. With the release of Compliance Operator 1.7.0, BSI compliance checks for Block SYS.1.6 Containerization and Block APP.4.4 Kubernetes are now available. For more information, see link:https://access.redhat.com/articles/7045834[*BSI Quick Check*].  
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/compliance-supported-profiles.adoc
M	modules/running-compliance-scans.adoc
M	security/compliance_operator/co-management/compliance-operator-installation.adoc
M	security/compliance_operator/compliance-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging security/compliance_operator/compliance-operator-release-notes.adoc
Auto-merging security/compliance_operator/co-management/compliance-operator-installation.adoc
Auto-merging modules/running-compliance-scans.adoc
CONFLICT (content): Merge conflict in modules/running-compliance-scans.adoc
Auto-merging modules/compliance-supported-profiles.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-13641: Compliance Operator 1.7.0 release

Details

In response to this:

/cherry-pick enterprise-4.13

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: #92420 failed to apply on top of branch "enterprise-4.12":

Applying: OSDOCS-13641: Compliance Operator 1.7.0 release
.git/rebase-apply/patch:18: trailing whitespace.
Increasing the memory limit for the Compliance Operator or the scanner pods is needed if the default limits are not sufficient and the Operator or scanner pods are ended by the Out Of Memory (OOM) process. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/security_and_compliance/compliance-operator#compliance-increasing-operator-limits_compliance-troubleshooting[Increasing Compliance Operator resource limits]. 
.git/rebase-apply/patch:89: trailing whitespace.
BSI (Bundesamt für Sicherheit in der Informationstechnik, Germany’s Federal Office for Information Security) compliance is legally mandated under Germany’s IT Security Act (IT-Sicherheitsgesetz) for critical infrastructure sectors like energy, healthcare, and telecommunications. With the release of Compliance Operator 1.7.0, BSI compliance checks for Block SYS.1.6 Containerization and Block APP.4.4 Kubernetes are now available. For more information, see link:https://access.redhat.com/articles/7045834[*BSI Quick Check*].  
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/compliance-supported-profiles.adoc
M	modules/running-compliance-scans.adoc
M	security/compliance_operator/co-management/compliance-operator-installation.adoc
M	security/compliance_operator/compliance-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging security/compliance_operator/compliance-operator-release-notes.adoc
Auto-merging security/compliance_operator/co-management/compliance-operator-installation.adoc
CONFLICT (content): Merge conflict in security/compliance_operator/co-management/compliance-operator-installation.adoc
Auto-merging modules/running-compliance-scans.adoc
CONFLICT (content): Merge conflict in modules/running-compliance-scans.adoc
Auto-merging modules/compliance-supported-profiles.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-13641: Compliance Operator 1.7.0 release

Details

In response to this:

/cherry-pick enterprise-4.12

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-sigs/prow repository.

[stevsmit]

/cherry-pick enterprise-4.13

[stevsmit]

/cherry-pick enterprise-4.12

[openshift-cherrypick-robot]

@stevsmit: #92420 failed to apply on top of branch "enterprise-4.13":

Applying: OSDOCS-13641: Compliance Operator 1.7.0 release
.git/rebase-apply/patch:18: trailing whitespace.
Increasing the memory limit for the Compliance Operator or the scanner pods is needed if the default limits are not sufficient and the Operator or scanner pods are ended by the Out Of Memory (OOM) process. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/security_and_compliance/compliance-operator#compliance-increasing-operator-limits_compliance-troubleshooting[Increasing Compliance Operator resource limits]. 
.git/rebase-apply/patch:89: trailing whitespace.
BSI (Bundesamt für Sicherheit in der Informationstechnik, Germany’s Federal Office for Information Security) compliance is legally mandated under Germany’s IT Security Act (IT-Sicherheitsgesetz) for critical infrastructure sectors like energy, healthcare, and telecommunications. With the release of Compliance Operator 1.7.0, BSI compliance checks for Block SYS.1.6 Containerization and Block APP.4.4 Kubernetes are now available. For more information, see link:https://access.redhat.com/articles/7045834[*BSI Quick Check*].  
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/compliance-supported-profiles.adoc
M	modules/running-compliance-scans.adoc
M	security/compliance_operator/co-management/compliance-operator-installation.adoc
M	security/compliance_operator/compliance-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging security/compliance_operator/compliance-operator-release-notes.adoc
Auto-merging security/compliance_operator/co-management/compliance-operator-installation.adoc
Auto-merging modules/running-compliance-scans.adoc
CONFLICT (content): Merge conflict in modules/running-compliance-scans.adoc
Auto-merging modules/compliance-supported-profiles.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-13641: Compliance Operator 1.7.0 release

Details

In response to this:

/cherry-pick enterprise-4.13

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-sigs/prow repository.

[openshift-cherrypick-robot]

@stevsmit: #92420 failed to apply on top of branch "enterprise-4.12":

Patch is empty.
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To record the empty patch as an empty commit, run "git am --allow-empty".
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"

Details

In response to this:

/cherry-pick enterprise-4.12

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-sigs/prow repository.

[stevsmit]

/cherry-pick enterprise-4.12

[openshift-cherrypick-robot]

@stevsmit: #92420 failed to apply on top of branch "enterprise-4.12":

Applying: OSDOCS-13641: Compliance Operator 1.7.0 release
.git/rebase-apply/patch:18: trailing whitespace.
Increasing the memory limit for the Compliance Operator or the scanner pods is needed if the default limits are not sufficient and the Operator or scanner pods are ended by the Out Of Memory (OOM) process. For more information, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/security_and_compliance/compliance-operator#compliance-increasing-operator-limits_compliance-troubleshooting[Increasing Compliance Operator resource limits]. 
.git/rebase-apply/patch:89: trailing whitespace.
BSI (Bundesamt für Sicherheit in der Informationstechnik, Germany’s Federal Office for Information Security) compliance is legally mandated under Germany’s IT Security Act (IT-Sicherheitsgesetz) for critical infrastructure sectors like energy, healthcare, and telecommunications. With the release of Compliance Operator 1.7.0, BSI compliance checks for Block SYS.1.6 Containerization and Block APP.4.4 Kubernetes are now available. For more information, see link:https://access.redhat.com/articles/7045834[*BSI Quick Check*].  
warning: 2 lines add whitespace errors.
Using index info to reconstruct a base tree...
M	modules/compliance-supported-profiles.adoc
M	modules/running-compliance-scans.adoc
M	security/compliance_operator/co-management/compliance-operator-installation.adoc
M	security/compliance_operator/compliance-operator-release-notes.adoc
Falling back to patching base and 3-way merge...
Auto-merging security/compliance_operator/compliance-operator-release-notes.adoc
Auto-merging security/compliance_operator/co-management/compliance-operator-installation.adoc
CONFLICT (content): Merge conflict in security/compliance_operator/co-management/compliance-operator-installation.adoc
Auto-merging modules/running-compliance-scans.adoc
CONFLICT (content): Merge conflict in modules/running-compliance-scans.adoc
Auto-merging modules/compliance-supported-profiles.adoc
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 OSDOCS-13641: Compliance Operator 1.7.0 release

Details

In response to this:

/cherry-pick enterprise-4.12

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-sigs/prow repository.