Epic Goal

• Support installing OKD SCOS using agent-based installer (ABI)

Why is this important?

• OKD SCOS is one of the type shipped for OKD. We already added the ABI support for the other type, OKD FCOS, in AGENT-367

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. Stable SCOS release pipeline is required.

Open questions::

1. How would be possible to retrieve the SCOS release and embed them in the installer metadata (required also for disconnected installations)

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>