Critical Epic Goal
- Collect all issues together that are needed before ACS can start to use Clair V4 as its container scanner.
Why is this important?
- Currently ACS is using a modified version of Clair V2 and Quay/Quay.io/container registry/HACBS etc are using Clair V4, in order to reduce technical debt and increase consistency across RH regards to security, ACS is planning to use Clair V4.
- Identifying the issues that are needed before that change can happen is useful to generate a timeline and divide work out across teams.
Acceptance Criteria
- Clair V4 should be on feature parity with ACS's scanner.
- There should be no blocking issues that prevent full adoption of Clair V4 by ACS.
Dependencies (internal and external)
- ACS scanner (https://github.com/stackrox/scanner)
- Claircore (https://github.com/quay/claircore)
- TODO: Add projects that depend on stackrox/scanner.
Previous Work (Optional):
Open questions::
- How much of this work will be the responsibility of the Clair/ACS team?
- How do we communicate / align with the ACS team during development?
Â
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
