Skip to content
代码片段 群组 项目
未验证 提交 e174ec66 编辑于 作者: Russell Dickenson's avatar Russell Dickenson 提交者: GitLab
浏览文件

Merge branch 'nilieskou/extend_ocs_doc' into 'master'

No related branches found
No related tags found
无相关合并请求
......@@ -15,9 +15,11 @@ DETAILS:
## Enable operational container scanning
You can use operational container scanning to scan container images in your cluster for security vulnerabilities. You
can enable the scanner to run on a cadence as configured via the `agent config`, or setup `scan execution policies` within a
project that houses the agent.
You can use operational container scanning (OCS) to scan container images in your cluster for security vulnerabilities.
Starting from GitLab Agent release 16.9, OCS uses a [wrapper image](https://gitlab.com/gitlab-org/security-products/analyzers/trivy-k8s-wrapper) around [Trivy](https://github.com/aquasecurity/trivy) to scan images for vulnerabilities.
Before GitLab 16.9, OCS directly used the [Trivy](https://github.com/aquasecurity/trivy) image.
OCS can be configured to run on a cadence by using `agent config` or a project's scan execution policy.
NOTE:
If both `agent config` and `scan execution policies` are configured, the configuration from `scan execution policy` takes precedence.
......@@ -160,6 +162,13 @@ You must have at least the Developer role.
To scan private images, the scanner relies on the image pull secrets (direct references and from the service account) to pull the image.
## Limitations
From GitLab Agent 16.9, Operational Container Scanning:
- handles Trivy reports of up to 100MB. For previous releases this limit is 10MB.
- is [disabled](../../../development/fips_compliance.md#unsupported-features-in-fips-mode) when the GitLab Agent runs in `fips` mode.
## Troubleshooting
### `Error running Trivy scan. Container terminated reason: OOMKilled`
......
0% 加载中 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册