aquasecurity/trivy

Support for CRI-O

Open

#3,004 opened on 2022年10月9日

GitHub で見る
 (3 comments) (0 reactions) (0 assignees)Go (35,000 stars) (371 forks)batch import
help wantedkind/featurepriority/backlog

説明

We are building an image-scanner K8s-operator, and all our clusters runs Openshift. Inspired by trivy-operator, which we cannot use for various reasons, we schedule scan jobs to scan container images currently in use by workloads in the cluster.

While the operator works, it could be optimized if trivy supported CRI-O, which is the CRI implementation that Openshift uses. This would allow us to scan the image pulled from the nodes image registry, by scheduling the scan job on the node that runs the pod in question.

Related issues: https://github.com/aquasecurity/trivy/issues/1282, https://github.com/aquasecurity/trivy/issues/851, https://github.com/aquasecurity/trivy-operator/issues/101

コントリビューターガイド

技術スタック
godockerkubernetes
領域
backendinfrastructuresecurity
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
fresh
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Go programmingknowledge of container runtimesfamiliarity with Kubernetes
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
30
調査方針
Investigate how trivy currently interacts with container runtimes (e.g., Docker) and extend support to CRI O. Review related issues #1282 and #851 for previous discussions. Key files to modify may include image pulling and scanning logic in the Go codebase. The maintainer has not provided specific implementation guidance, so the contributor should explore the existing architecture and propose a design.
Support for CRI-O · aquasecurity/trivy#3004 | Good First Issue