Feature Overview

• With the coming GA of Arm as a valid architecture to run OpenShift core services on we need to expand to have OpenShift Addons also functional on Arm
• Arm has or will be soon adopted in all the key cloud providers (AWS, Azure, GCE) as well as being picked up by key vendors (like Apple) and with typical savings of 40% costs and the very low power footprint we are already seeing major opportunities, our customers will expect full OpenShift functionality on this architecture
• Ideally in the future Arm build/test will be baked in i.e. it will happen as part of the standard development process but at this time there are already a set of Addons available that we need to ma

Goals

• Have programs (with sign off from relevant teams) to bring OpenShift Addons over to the Arm architecture, this could include but is not limited to:
  • Pipelines

• • GitOps

• • Runtimes

• • ACM

• • CodeReady Workspaces

• • odo

• • SeviceMesh

• • Serverless

• • ODF

• • Multus Plugins (SR-IOV, IPVLAN, Bridge with VLAN, Static IPAM)

• • ACS

Requirements

• (optional) A business case for each area to justify the effort
• SIgn off from Addon PM that this is work they will do
• Plan and Jira entries for work to be done/tracked by each of the teams

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