We're considering breaking compat between Ignition spec <= 2.x.y and v3.0.0. This is because of coreos/ignition#608. This would mean FCOS would only accept configs >=v3.0.0. This would mean users migrating from Container Linux would need to migrate their configs (i.e. could not boot the same config). That would include configs that are appended. Container Linux would only support 2.x configs through the rest of its lifetime.
Some consequences if we did that:
- Everyone would need to migrate configs. We expect that to some degree anyway for any reasonably complex config since some filesystem paths will change. An automated tool to help translate could do a "best effort" translation, but anyone taking advantage of weird use cases may not get what they are expecting.
- CL would need to support a branch of Ignition with spec 2.x through the rest of its life. This means backporting bugfixes to it.
Some consequences if we didn't do that:
- Either the 3.0.0+ configs (forever) carries the same lack of declarativeness or we have an imperfect translation step from 2.3.0 to 3.0.0. I don't think we can ship a broken translator.
What are people's thoughts on only shipping 3.0.0+? Note that the 3.0.0 spec is nowhere near finalized yet.
We're considering breaking compat between Ignition spec <= 2.x.y and v3.0.0. This is because of coreos/ignition#608. This would mean FCOS would only accept configs >=v3.0.0. This would mean users migrating from Container Linux would need to migrate their configs (i.e. could not boot the same config). That would include configs that are appended. Container Linux would only support 2.x configs through the rest of its lifetime.
Some consequences if we did that:
Some consequences if we didn't do that:
What are people's thoughts on only shipping 3.0.0+? Note that the 3.0.0 spec is nowhere near finalized yet.