-
Notifications
You must be signed in to change notification settings - Fork 393
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
Speed up Flatcar QEMU builds #924
Comments
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
/remove-lifecycle rotten |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@tormath1 Thoughts? |
@mdbooth that would be nice to see this - especially if we build Flatcar images without KVM in Github Actions. This issue is already tracked as part of the Cluster API Flatcar Roadmap (https://github.com/orgs/flatcar/projects/7/views/14) but it's not prioritized. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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/test-infra repository. |
Is your feature request related to a problem? Please describe.
Right now Flatcar QEMU build downloads ISO image via Packer, then inside the VM image is downloaded again by Flatcar installation script to install Flatcar to the disk and reboot. This is disk and network intensive and could possibly be improved.
Describe the solution you'd like
Perhaps it would be possible to use
"disk_image"
and"qemuargs"
Packer QEMU builder options to pass packer Ignition directly to the Packer QEMU builder to skip one level of indirection and get a VM directly booted with SSH available.One blocker for this might be that IIRC right now Flatcar does not offer uncompressed QEMU disk images, so we would either have to make them available or download and unpack the image manually before we run Packer. (EDIT: reported flatcar/Flatcar#791)
Here is the PoC solution which seem to work:
Additional context
If that happens, perhaps it should be contributed to https://github.com/flatcar-linux/flatcar-packer-qemu.
/kind feature
The text was updated successfully, but these errors were encountered: