Feature Overview

...

Goals

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

• It is quite an involved and fairly manual process for our customers to figure out their upgrade paths.  Given that clusters are being managed by ACM, the want is to have ACM take on and provide the upgrade ability, path, compliance for the managedclusters.  This includes the OCP versions that a customer is trying to upgrade to (e.g., EUS to EUS), and the add on operators installed on the managedclusters.
• Have ACM orchestrate the upgrades

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.

Step 1: Gather ACM spoke cluster data to be displayed inside of ACM hub clusters 

Spoke cluster LCM tab information needed in ACM:

• Cluster version and OCP channel the cluster is subscribed to
• Node information:
  • RHCOS version
  • Show the "state" of all nodes from bmh in openshift-machine-api namespace (this tells us if there is a node that was stuck in provisioning state)
  • Show the status of nodes from the output of 'oc get nodes'
  • MCPs assigned to each node (note: most worker nodes in Telco have 2 MCPs)
  • Show if the MCPs are paused(true or false)
• Show if any cluster operators are:
  • available: false
  • progressing: true
  • degraded: true
• Show all OLM based operators that are installed
  • their current version
  • the channel they are subscribed to
  • if they are set to manual or automated update

Step 2: Display an upgrade path for a spoke cluster

(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

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)?