Goal Summary:

ACS should be able to schedule OCPVirt profile.

Blockers:

In order to start with this feature the following 2 features need to be delivered in Compliance Operator. 

CMP-3993 - Ability to use rules written in CEL to build out of the box profile content - Scheduled for CO 1.9

CMP-3202 - Compliance Operator support for OCPVirt - Scheduled for CO 1.10

Goals and expected user outcomes:

The goal is to be able to schedule OCPVirt profile via ACS.

In order to do this ACS should be aware which clusters have OCPVirt running 

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.

<enter success criteria and/or KPIs here>

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>