-
Sub-task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
None
-
5
-
False
-
-
False
-
OCPSTRAT-465 - Agent-based Installer add cluster configs after booting image
-
-
-
Sprint 236, Sprint 238
Requirements:
- The unconfigured ignition should be the same as the existing ignition included in the agent.iso with the exception that only a select few ZTP assets are included:
- InfraEnv
- ClusterImageSet
- AgentPullSecret
NMStateConfig (if provided)(only for interactive install)
- Other assets like ClusterDeployment, AgentClusterInstall, etc are excluded and will be mounted into the host later on using the config ISO. See
AGENT-559. If the other assets are provided in the asset directory, they should be ignored. - The following services are not enabled in the ignition:
- apply-host-config.service
- start-cluster-installation.service
Acceptance Criteria:
- Integration test to verify unconfigured ignition file is created and includes
- InfraEnv
- ClusterImageSet
- Pull Secret
NMStateConfigs (if provided)
- Ignition can be used to generate a bootable agent.iso
- ISO can be generated using '
coreos-installer iso ignition embed' - Hosts booting this iso does not start cluster configuration
- ISO can be generated using '
Engineering Details:
- Existing Agent Ignition asset: https://github.com/openshift/installer/blob/master/pkg/asset/agent/image/ignition.go
- The existing Agent Ignition asset could be refactored to use the UnconfiguredIgnition as a base and add in the Cluster specific configuration in its generate function.
- And enable services that were disabled in the UnconfiguredIgnition