Throughout the MCO, there are duplicate code paths for both Ignition v2 and Ignition v3. If my memory serves correct, when the upgrade from Ignition v2 -> Ignition v3 occurs, or a new MachineConfig written with Ignition v2 is created, the MCO converts it from Ignition v2 to Ignition v3. With this in mind, we can most likely remove the Ignition v2 code paths so that we no longer have to maintain two separate paths. This will simplify our codebase by removing code that is not really used anymore.

Done When:

• Feasibility of removal is conclusively determined.
• Ignition v2 code paths are removed from all MCO components.
• The Ignition v2 vendored source is removed from our repository.