Epic Goal

• ACM 2.6 released with OCP 4.11 (N)
• ACM 2.6.Z will include support for OCP 4.12 (N+1)
• The goal is to deliver a 2.6.Z at the same time that OCP 4.12 goes to GA. Literally 2.6.Z on the same day as OCP 4.12 would be ideal.

Why is this important?

• Customers have come to expect that the management layer is ready and able to handle the newest OCP release when it comes out.

Scenarios

1. As an ACM DevOps engineer, during OCP 4.12 RC, I can ensure ACM 2.6.Z canary testing is running against OCP 4.12.
2. As a customer running a hub on ACM 2.6.Z, I can deploy a new OCP 4.12 cluster on the same day when the OCP 4.12 goes to GA.
3.  

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Clean passes on Canary tests run against ACM 2.6.Z with OCP 4.12 as Hub and as Managed Cluster
• Support Matrix updates on the ACM 2.6 support matrix: https://access.redhat.com/articles/6968787

Dependencies (internal and external)

1. OCP 4.12 GA date - JANUARY 17, 2023: (get on VPN) https://pp.engineering.redhat.com/pp/product/openshift/release/openshift-4.12/schedule/tasks

Previous Work (Optional):

1. …

Open questions:

1. What bugs will be found?

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>