IBI generate a containerfile #9682
Conversation
# Background / Context With openshift-kni/lifecycle-agent#815 we can generate seed images that are also bootc images. Using a simple `Containerfile`, we can FROM these images, add a cluster configuration, and get a fully bootable cluster # Issue / Requirement / Reason for change This Containerfile needs to be written manually # Solution / Feature Overview The installer can help the user write this Containerfile. # Implementation Details We add a new subcommand, `containerfile`, to the `image-based create` command. This command is similar to the config-image command, but instead of generating an ISO, it generates a Containerfile that can be used to build the configured-seed image. # Other Information - The installer does not actually build the image, this is left to the user. The installer only generates the Containerfile. - The Containerfile currently needs to extract the tars. This is unnecessary, the lifecycle-agent should already do that during the seed build. There's no point in having those tars inside the image. - Changed some other unrelated IBI code to leverage Go's `embed`
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@omertuc: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Background / Context
With openshift-kni/lifecycle-agent#815 we can generate seed images that are also bootc images. Using a simple
Containerfile, we can FROM these images, add a cluster configuration, and get a fully bootable clusterIssue / Requirement / Reason for change
This Containerfile needs to be written manually
Solution / Feature Overview
The installer can help the user write this Containerfile.
Implementation Details
We add a new subcommand,
containerfile, to theimage-based createcommand.This command is similar to the config-image command, but instead of generating an ISO, it generates a Containerfile that can be used to build the configured-seed image.
Other Information
The installer does not actually build the image, this is left to the user. The installer only generates the Containerfile.
The Containerfile currently needs to extract the tars. This is unnecessary, the lifecycle-agent should already do that during the seed build. There's no point in having those tars inside the image.
Changed some other unrelated IBI code to leverage Go's
embed