You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: