Skip to content
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

Update to CoreOS ignition specification v3.4.0 #253

Open
Gerrit91 opened this issue Aug 13, 2024 · 3 comments
Open

Update to CoreOS ignition specification v3.4.0 #253

Gerrit91 opened this issue Aug 13, 2024 · 3 comments

Comments

@Gerrit91
Copy link
Contributor

We are actually transpiling ignition user data with the os-metal-extension with version 2.3.0.

Upstream there is already v3.4.0 available: https://coreos.github.io/ignition/specs/

In order to allow the migration and do not break existing images, we need to find a solution. For instance, we could programmatically run the ignition executor through the metal-hammer in the chroot of the os image. This way we would decouple the ignition binary installed on the images from our provisioning procedure.

@robertvolkmann
Copy link
Contributor

Are there any plans to remove Ignition and rely solely on Cloud-init, which has been included in the images for several years?

@majst01
Copy link
Contributor

majst01 commented Jan 20, 2025

I would like to stay with ignition, but as this issue states, with the newer spec

@robertvolkmann
Copy link
Contributor

robertvolkmann commented Jan 20, 2025

Cluster API only supports ignition v2 and no one is maintaining it. Additional, cloud-init is not working anymore in our images, see comments in #272.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants