Skip to content

Make Scanner always active #129

Description

@r2dedios

For future work, we're considering to move the scanner from a single-execution component to an always active microservice. This has several impacts: Scanner will no be run from CronJobs anymore, the scanner will be always available listening for requests and a new scan process can be triggered from the API if it's needed

Metadata

Metadata

Assignees

Labels

choreenhancementNew feature or requestholdSomething needs to block this issue from merging

Fields

No fields configured for Feature.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions