Done When:

• We implement a solution that mitigates the node disruptions when applying Machine Configs.

Notes:

• MVP: when a MachineOSBuild object is deleted, the corresponding image in the registry should also be deleted, whether internal or external
• Mid term: have good documentation around user-driven prunes, and what can/cannot be pruned
• Mid term: have an opt-in/opt-out mechanism for auto pruning, where builds not in use and x versions old are deleted automatically
• Nice to have: tag latest (and maybe latest-1) builds for pools, so the user can easily refer to the latest build and know what not to prune
• Nice to have: have user-pruned images automatically reflect back on the MachineOSBuild
• Long term: user defined prune logic