Epic Goal

• Allow the user to interactively configure the mirror registries after booting the ISO.

Why is this important?

• In cases where the cluster is to be installed in a disconnected environment, but the ISO is generated in a connected environment (or a different disconnected environment), mirror registry configuration is required that can only be validated once the ISO is actually booted.

Scenarios

1. The user generates the agent ISO using a laptop in a regular connected network, without specifying any mirror registries. They then attempt to install the cluster using the ISO in a disconnected environment. They are able to configure the registry mirror through the console at the same time as configuring the network settings (AGENT-385) while booting the ISO.

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. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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>