XML

Word

Printable

Details

Type: Epic
Resolution: Done
Priority: Blocker
Fix Version/s: openshift-4.12
Affects Version/s: None
Component/s: None
Labels:

Epic Name:
Disconnected automated installation
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Color Status:
Not Selected
Epic Status:
Done
Feature Link:
OCPPLAN-8150 - Agent-Based Installer GA
Flagged:

Impediment
Parent Link:
OCPPLAN-8150Agent-Based Installer GA
Hierarchy Progress:
100
Hierarchy Progress Bar:

100% 100%
Release Note Text:

Hide
You can perform an Agent-based installation in a disconnected environment. To create an image that is used in a disconnected environment, the `imageContentSources` section in the ` install-config.yaml` must contain the mirror information or `registries.conf` file if you are using ZTP manifests. The actual configuration settings to use in these files are supplied by either the `oc adm release mirror` or `oc mirror` command. For more information, see xref:../../installing/installing_with_agent_based_installer/understanding-disconnected-installation-mirroring.adoc[Understanding disconnected installation mirroring].

Show
You can perform an Agent-based installation in a disconnected environment. To create an image that is used in a disconnected environment, the `imageContentSources` section in the ` install-config.yaml` must contain the mirror information or `registries.conf` file if you are using ZTP manifests. The actual configuration settings to use in these files are supplied by either the `oc adm release mirror` or `oc mirror` command. For more information, see xref:../../installing/installing_with_agent_based_installer/understanding-disconnected-installation-mirroring.adoc[Understanding disconnected installation mirroring].
Release Note Type:
Feature
Release Note Status:
Done
Target Version:

openshift-4.11

Release Blocker:
Approved

SFDC Cases Links:
SFDC Cases Counter:

Description

Ability to perform disconnected first cluster installation in the automated flow

Epic Goal

Generate an ISO that uses a disconnected mirror and can be fully deployed without access to quay

Why is this important?

A lot of secure environments do not allow connectivity to Red Hat / Quay registries. In order to enable customers with such environments to deploy their first cluster, we need to allow them to install from a mirror

Scenarios

User sets up a mirror containing the release and any operator they wish to deploy after installation. User sets up the input to use the mirror registry, then generates the iso with openshift-install agent create image. Finally, the user boots the systems with the generated ISO and gets a succesful OCP cluster installation that does not connect to internet resources.

Acceptance Criteria

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

Dependencies (internal and external)

Previous Work (Optional):

Open questions::

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>