Feature Overview

In order for the agents to be easily deployable and managable in an ACM context, it needs to be integrated as a Multi Cluster Engine (MCE) workload.

Goals

Deploying and managing the agent on workload clusters can be tedious depending on the amount of clusters. ACM provides a proper solution for Red Hat customers to do exactly that. The goal is to integrate the agent into ACM's mechanisms (MCE), so that ACM customers can easily use the agent with their managed clusters.

Requirements

Use Cases

• As a user of ACM, I want to distribute the agent according to my ACM policies and have ACM take care of deployment and configuration of the agent
• As a user of OpenShift, I want an easy mechanism for the distribution of my agents

Out of scope

<Defines what is not included in this story>

Dependencies

<Link or at least explain any known dependencies.>

Background, and strategic fit

<What does the person writing code, testing, documenting need to know?>

Assumptions

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Customer Considerations

<Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation/QE Considerations

<What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)?>

<Does this feature have a doc impact? Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact?>

<Are there assumptions being made regarding prerequisites and dependencies?>

<Are there assumptions about hardware, software or people resources?>

Impact

<If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Definition of Ready

• The objectives of the feature are clearly defined and aligned with the business strategy.
• All feature requirements have been clearly defined by Product Owners.
• The feature has been broken down into epics.
• The feature has been stack ranked.
• Definition of the business outcome is in the Outcome Jira (which must have a parent Jira).

• …