There's a few API changes we've identified that's best if it can happen before GA, so it would be easier to update later:

• Namespace MOSC / MOSB - this is required for Hypershift if we'd like to have the management cluster build for multiple hosted clusters
  • We have determined that this is not needed as Hypershift will not need to leverage namespaced objects, but rather configmap-embedded objects to decouple the need for management cluster to have the corresponding API.
• Make the baseImagePullSecret field optional; inherits from global-pull-secret by default.
  • This is still nice to have for GA
• Make optional fields for entitlement creds (this may need additional checks to see if it's required)
  • This has been determined to be not necessary as there is no existing use case for them
• Consolidate / unified on-cluster and off-cluster flows into the same API field?
  • After discussing this, there's no need for this as the on-cluster and off-cluster workflows do not directly intersect at this time. We would like to eventually move the workflow to MachineConfigNodes instead of using annotations on the node object/osimageurl
• Separate the Containerfile field?
• Add a BuildStrategy field to MachineOSConfigs to allow a cluster admin to specify additional information about how the build should be performed. For example, if we want to support OpenShift Pipelines in the future, a cluster admin will need to specify additional information there.
  • This will need additional work once we have a more robust CI story
• Remove inline Containerfiles from MachineOSConfigs and have them live in ConfigMaps instead and have a reference placed in the MachineOSConfig that points to the ConfigMap(s).
  • We will revisit this once we have a better CI story as well, based on the discussion during image mode sync.
• Fix spec validation for renderedImagePushspec (OCPBUGS-37793)