Addressing 1:1 Dependency Between MCO and Butane

coreos / butane

Butane translates human-readable Butane Configs into machine-readable Ignition Configs.

https://coreos.github.io/butane/

Apache License 2.0

255 stars 70 forks source link

Addressing 1:1 Dependency Between MCO and Butane #520

Open yasminvalim opened 8 months ago

yasminvalim commented 8 months ago

This issue intends to investigate and discuss the 1:1 dependency between MCO and Butane. The objective is to understand this dependency and explore the possibility of untangling it to ensure a smoother release process.

However, if there is no immediate solution, we will take a few actions to prevent unplanned releases:

Incorporate GA release dates into coreos-packages Google agenda.
Set reminders in Slack as the GA release dates approach.

travier commented 5 months ago

There is a 1:1 match between the openshift variants and openshift releases to let users use a spec version matching their openshift release at all times, without having to think about compatibility. A config written with the 4.15.0 spec should work on a 4.15.0 (and later) cluster, etc.