During an upgrade, the machine-os-builder deployment doesn't roll out an updated pod with the updated image. This leads to issues with changes across versions.

    4.20

    Everytime

    1. Upgrade from 4.18.z to 4.19, the MOSB will fail to build a new image
    2.
    3.
    

    "Unhandled Error" err="Adding MachineOSBuild \"worker-a569583364a7f1a8e6ade1b77541cd6
a\" failed: Syncing MachineOSBuild \"worker-a569583364a7f1a8e6ade1b77541cd6a\" failed: could not start build for MachineOSBuild \"worker
-a569583364a7f1a8e6ade1b77541cd6a\": imagebuilder could not start build for MachineOSBuild \"worker-a569583364a7f1a8e6ade1b77541cd6a\": 
imagebuilder for MachineOSBuild \"worker-a569583364a7f1a8e6ade1b77541cd6a\" encountered an error: could not start job: could not prepare
 for MachineOSBuild \"worker-a569583364a7f1a8e6ade1b77541cd6a\": could not create ephemeral build objects: could not convert etc/contain
ers registries files into ConfigMap \"etc-policy-worker-a569583364a7f1a8e6ade1b77541cd6a\": parsing rendered MC Ignition config failed w
ith error: failed to parse Ignition config: parsing Ignition config failed: unknown version. Supported spec versions: 2.2, 3.0, 3.1, 3.2
, 3.3, 3.4"

    New image should be built and rolled out to the nodes

    Noticed that we don't always call ApplyDeployment that does the diff check needed to update the container image and pod rollout on an upgrade