Feature Overview

...

Goals

ACM to act as a centralized store for all managed cluster events.

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Main success scenarios - high-level user stories
• Alternate flow/scenarios - high-level user stories
• ...

Questions to answer

• ...

Out of Scope

• ...

Background, and strategic fit

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

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

           We need to document how to enable this feature maybe as part of ACM core functionality or as add-on

• Does this feature have a doc impact?

           Yes this feature will have a doc impact.

• New Content, Updates to existing content, Release Note, or No Doc Impact

• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?

 This feature will help streamline any integration external system can access  Openshift and Kubernetes objects on a real-time basis using the centralized Hub Cluster.

• What reference material might a customer want/need to complete [action]?

• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?