Feature Overview

Create a dynamic and easy to use page to show which of the various components in ACM and its associated offerings (MCE, HCP, etc) are supported together.

Allow documentation teams to spend less time updating this by introducing an automated backend to build the outcome.

Ensure cross-squad participation allowing experts to update their respective sections more accurately.

Goals

Provide customers and field with a dynamic single place of truth to find supportability across anything ACM touches. This will continue the work currently in:

https://access.redhat.com/articles/7086905

https://access.redhat.com/articles/7086906

https://access.redhat.com/support/policy/updates/openshift_operators 

Allow documentation teams to spend less time updating this by introducing an automated backend to build the outcome.

Ensure cross-squad participation allowing experts to update their respective sections more accurately.

Requirements

 
TBA

(Optional) Use Cases

TBA

Questions to answer

TBA

Out of Scope

TBA

Background, and strategic fit

To make it as easy as possible for customers and field to see and understand which parts of ACM are supported in which environments. This helps to make it easier to support multi-cloud deployments and encourages the use of ACM for centralised management.

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Current matrices are excellent but time consuming to maintain. One consideration for docs is that the ownership can remain with them, but much of the content sourcing should come from product experts and owners. So we need to make it easier for them to contribute to that and subsequently for docs to get that info into this dynamic tooling