Goal Summary:

There are a number of periodic jobs that are scheduled within the Central container:

• Scheduled vulnerability report generation
• External backup execution
• Compliance scan scheduling
• Database cleanup/pruning tasks
• Certificate rotation checks

Challenges we have with these jobs running inside of Central:

• Blast radius: If any job ran away with resources (CPU/memory), it would negatively impact the API server and data ingress, potentially causing an outage of both.
• One replica: There can only be one copy of these jobs running, making it more challenging to run more than one copy of Central.

These need to be broken into separate workload(s).

Goals and expected user outcomes:

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

• These jobs no longer impact the operational availability of Central (note that they could still impact DB performance or availability)
• Users observe separate workloads in their StackRox namespace for these jobs

Acceptance Criteria:

A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

<enter general Feature acceptance here>

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

• Higher availability for Central
• Fewer and more consistent resources consumed by Central

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Out of Scope (Optional):

High-level list of items that are out of scope. Initial completion during Refinement status.

<your text here>