Feature Overview

Support for integrating Ansible automation with ARO cluster updates in ACM

Goals

• ARO (Classic) can be upgraded like a regular self-managed OCP
• Now that ARO cluster updates are supported in ACM 2.12+
• Therefore the ACM + Ansible integration prehook and posthook can be enabled for this type of cluster as well

Requirements

(Optional) Use Cases

This Section:

• From the Clusters list I want to click the Upgrade button (when available for the ARO) and be offered the opportunity to upgrade with automation hooks
• Multiselect of clusters including ARO should respond accordingly with the update automation hooks options.

Questions to answer

• We understand that looking ahead, there will be some work to do to differentiate between ARO Classic and ARO HCP. This work has not been sized yet based on the timeline of ARO HCP and how exactly that cluster 'type' will manifest itself into the managed cluster inventory. I would say this remains an open question for now.

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