Epic Goal

• The real goal here is to bring RHACM's Discovery capability to GA
• We know one of the impediments is the API supportability, which is currently at v1alpha.

Why is this important?

• We want to keep the Discovery feature in ACM and expand on it in the future.
• We want to signal to the customers/market that this feature has a longer term position as enabling the fast onboarding of existing clusters.

Scenarios

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• APIs are supported at v1beta1
• Console removes the tech preview banners
• DOC removes the tech preview verbiage

Dependencies (internal and external)

1. c.rh.c
2. OCM Credentials

Previous Work (Optional):

1. …

Open questions:

1. what other changes are necessary to ensure the production/GA capability of the code?

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>