To release a feature as General Availability (GA), the openshift/api has a `verify-feature-promotion` test run on all Feature Gate (FG) graduation PRs. The test verifies whether the component readiness score for the FG is showing an appropriate level of confidence that the feature is ready to GA. This task involves monitoring the tests contributing to the component readiness of the Status Reporting FG to ensure bugs are identified and remediated in an appropriate amount of time so that the feature can be graduated to default in the 4.20 release.

Note that this card has a "Work included" list instead of the typical "Done when" list. This is because this card is more to track the time involved with monitoring regression tests and to document any relevant comments/updates regarding component readiness rather than working on a tangible deliverable.

Work included:

• Track the pass rate of the Status Reporting tests and investigate failures, create bugs, and communicate the status of the tests.
• Monitor the results of the `verify-feature-promotion` test on the PR for MCO-XXXX (once it is created) to ensure tests are encompassing of expected graduation requirements.

Resources:

• The MCN FG's 4.20 Sippy dashboard can be found here. Changing some filters will show the Status Reporting feature, but this is a good starting dashboard.
• If any manual triggering of jobs is needed, the ganway-cli tool can be used.
  • Note that the `MY_APPICI_TOKEN` credential referenced in the README is just the CI secret referred to in the MCO onboarding doc.
• Information on the component readiness requirements can be found defined in the API repo here, and information specific to the process for 4.19 as defined by the Technical Release Team (TRT) can be found in this document.