Feature Overview

...

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• Edge manager should be decoupled from ACM so that it is no longer installed or affected by MCH and separate installation of edge manager is not influenced

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:

• A fresh install of ACM without Edge management installed does not install edge manager CRDs or resources
• A fresh install of ACM with edge manager installed afterwards does not affect the decoupled edge manager deployment
• An upgrade of edge manager from 2.15.0 to 2.15.1 with edge manager not installed removes all references to edge manager from ACM
• An upgraded ACM installation on 2.15.0 to 2.15.1 does not install any edge manager CRDs or resources, but allows them to exist on the cluster without being affected
• Other components which need to be aware of edge manager are able to have that flag passed to their resources

Questions to answer

• Will the new edge manager resources be in a separate namespace so that they are not affected by any un installations that are performed by ACM 2.15.1

Out of Scope

• …

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

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)?
• Does this feature 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)?
• 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)?