-
Notifications
You must be signed in to change notification settings - Fork 30
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
[RFE] Publish official Kubevirt images #1358
Comments
@lukasmrtvy would you be interested to implement this by yourself? Here's an example with Scaleway: flatcar/scripts#1683 |
Hello, the official production image works (example: https://alpha.release.flatcar-linux.net/amd64-usr/current/flatcar_production_image.bin.bz2), leveraging the coreos-cloudinit fallback implementation. I think you mean adding support for Ignition to work with Flatcar deployed as a KubeVirt VM, which will be required as an oem image. @lukasmrtvy The Kubevirt CDI helper usually supports .gz or .xz implementation, do you have a preference for the compression format? Some documentation would be needed to give an example workflow though, with both Ignition and the coreos-cloudinit. Also to mention that Flatcar supports only cloudInitConfigDrive data source: https://kubevirt.io/user-guide/virtual_machines/startup_scripts/#data-sources Thank you, |
As Ignition supports KubeVirt, add a custom oem for it and also the required parts to be able to build an image in .qcow2 format and .gz compression. Fixes: flatcar/Flatcar#1358 Signed-off-by: Adrian Vladu <avladu@cloudbasesolutions.com>
As Ignition supports KubeVirt, add a custom oem for it and also the required parts to be able to build an image in .qcow2 format and .gz compression. Fixes: flatcar/Flatcar#1358 Signed-off-by: Adrian Vladu <avladu@cloudbasesolutions.com>
As Ignition supports KubeVirt, add a custom oem for it and also the required parts to be able to build an image in .qcow2 format that is already using internal .qcow2 gzip compression. Fixes: flatcar/Flatcar#1358 Signed-off-by: Adrian Vladu <avladu@cloudbasesolutions.com>
As Ignition supports KubeVirt, add a custom oem for it and also the required parts to be able to build an image in .qcow2 format that is already using internal .qcow2 gzip compression. Fixes: flatcar/Flatcar#1358 Signed-off-by: Adrian Vladu <avladu@cloudbasesolutions.com>
As Ignition supports KubeVirt, add a custom oem for it and also the required parts to be able to build an image in .qcow2 format that is already using internal .qcow2 gzip compression. Fixes: flatcar/Flatcar#1358 Signed-off-by: Adrian Vladu <avladu@cloudbasesolutions.com>
Current situation
Flatcar does not work ( officially ) in Kubevirt and other platforms based on Kubevirt ( https://github.com/harvester/harvester ), because of the missing
flatcar.oem.id=kubevirt
parameter in grub.Impact
Mid
Ideal future situation
Official Kubevirt images are published
Implementation options
X
Additional information
Images based on https://github.com/kubernetes-sigs/image-builder/ are working correctly
The text was updated successfully, but these errors were encountered: