mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
17 lines
1.3 KiB
Plaintext
17 lines
1.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * security/compliance_operator/co-scans/compliance-scans.adoc
|
|
|
|
:_mod-docs-content-type: CONCEPT
|
|
[id="compliance-scansetting-cr_{context}"]
|
|
= `ScanSetting` Custom Resource
|
|
|
|
The `ScanSetting` Custom Resource now allows you to override the default CPU and memory limits of scanner pods through the scan limits attribute. The Compliance Operator will use defaults of 500Mi memory, 100m CPU for the scanner container, and 200Mi memory with 100m CPU for the `api-resource-collector` container. To set the memory limits of the Operator, modify the `Subscription` object if installed through OLM or the Operator deployment itself.
|
|
|
|
To increase the default CPU and memory limits of the Compliance Operator, see _Increasing Compliance Operator resource limits_.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
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].
|
|
====
|