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
While ct is deprecated and not used anymore (even LTS can support Ignition 3 now) - we might be interested to drop ct from Mantle to only use Butane.
Impact
Scaleway test suite can't be implemented without hacks as Mantle flight relies on ct platform -> we can use a ctplatform.Custom but we need then to implement some logic to convert the Scaleway metadata to the expected "custom" format.
Ideal future situation
No more ct configuration inside Mantle, everything relies on Butane or raw Ignition.
Implementation options
Remove ctplatform dependency from ctplatform
Rewrite ct configuration to butane configuration (git grep ContainerLinuxConfig)
Scaleway test suite can't be implemented without hacks as Mantle flight relies on ct platform -> we can use a ctplatform.Custom but we need then to implement some logic to convert the Scaleway metadata to the expected "custom" format.
Can you link to some code? I don't understand what ctplatform and why it would require hacks to support scaleway.
If we remove ct from mantle we can't be sure that we won't break users who still have old ignition configs. I'm sure they haven't migrated.
Current situation
While
ct
is deprecated and not used anymore (even LTS can support Ignition 3 now) - we might be interested to dropct
from Mantle to only use Butane.Impact
Scaleway test suite can't be implemented without hacks as Mantle flight relies on
ct
platform -> we can use actplatform.Custom
but we need then to implement some logic to convert the Scaleway metadata to the expected "custom" format.Ideal future situation
No more
ct
configuration inside Mantle, everything relies on Butane or raw Ignition.Implementation options
ctplatform
dependency fromctplatform
git grep ContainerLinuxConfig
)See also: coreos/coreos-assembler@f0e4985
The text was updated successfully, but these errors were encountered: