OCP/Telco Definition of Done
Epic Template descriptions and documentation.

Epic Goal

• Enable ARM support for Bare Metal deployments, including kubernetes-nmstate in downstream OCP

Why is this important?

• It enables additional users to consume kubernetes-nmstate

Scenarios

1. A customer is running OCP on ARM and wants to use kubernetes-nmstate to configure node networking.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Images for ARM must be available in OperatorHub

Dependencies (internal and external)

1. We need builds of kubernetes-nmstate on ARM.
2. OpenShift Container Platform 4.x Tested Integrations (for aarch64, ARM) 

Previous Work (Optional):

1. Upstream kubernetes-nmstate has added support for ARM, so there shouldn't be any code changes required.

Open questions::

1. Is ARM even a supported architecture for OCP?
2. What is the process to enable ARM builds for an OperatorHub operator?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>