Background

When creating Machines currently, we are forced to set cloud init configuration. However, this is not correct. The AWS provider can handle ignition and we should be treating the Machine configuration as ignition.

We should prevent the cloud init configuration from being used within OpenShift's cluster api namespace since we know that cloud init is not supported by RHCOS.

This validation need not apply to other namespaces as this may prevent users managing non-OpenShift clusters from our clusters.

Steps

• Ensure that the ignition format is set within the user data secret
• Ensure support for ignition v3 is merged upstream
• Set the ignition version to the correct version (should be 3.4)
• Enforce the ignition configuration via webhooks for the openshift-cluster-api namespace

Stakeholders

• Cluster infra

Definition of Done

• Machines on AWS are forced to set ignition configuration rather than cloud init

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>