-
Notifications
You must be signed in to change notification settings - Fork 29
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
Support Flatcar #302
Comments
Hi, thanks for working on this. I am a Flatcar maintainer and I am involved on Cluster API topics too. For Flatcar support to work, we first need to get Ignition Proxmox support. You can track this here: flatcar/scripts#1783 (cross-ref: flatcar/Flatcar#1040) |
@tormath1 yes, I know that, |
What are your hacks? For what is worth, Flatcar + CAPO works fine at the moment. Feel free to join the Flatcar Matrix channel or #flatcar channel on Kubernetes Slack to discuss about this more interactively (https://github.com/flatcar/flatcar?tab=readme-ov-file#chat) |
networkd config should be adjusted so it can support our current features: Ref: https://www.freedesktop.org/software/systemd/man/latest/systemd.network.html |
Flatcar images are now available on Proxmox: https://www.flatcar.org/releases#release-4152.0.0 |
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
To support Flatcar, we must ensure that Proxmox can load the ignition data into the VM.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
we have a way of injecting an ISO into the VM; while providing ignition data.
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: