New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom deploy: do not require an ISO #193
Custom deploy: do not require an ISO #193
Conversation
/uncc |
It is possible to only use PXE artefacts, in which case we need to generate an ignition file, but don't need to customize the ISO.
/cc @kirankt |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dtantsur, kirankt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold need pkgs update first #192 |
/test e2e-metal-ipi |
/test e2e-metal-ipi-virtualmedia |
/test e2e-metal-ipi |
/unhold |
/test e2e-metal-ipi-virtualmedia |
Add support for noop management and manual-management
It is possible to only use PXE artefacts, in which case we need to
generate an ignition file, but don't need to customize the ISO.
Increase verbosity of configure-coreos-ipa for debugging.