Background

Currently, CAPA is ahead of MAPA in its support for various options in the AWS metadata service configuration, see here.

To avoid having to return errors when these options are configured in CAPA (and to improve backwards compatibility, we should look to understand what these options do, backport them into MAPA, and then update the conversion logic to remove the errors.

Steps

• Understand the implications of the metadata service options configuration that CAPA has that we do not.
• Implement the new fields in the AWSMachineProviderConfig
• Plumb the values into MAPA
• Validate the new API fields in the MAPI webhooks
• Remove the erros in the CAPI2MAPI when these fields are populated

Stakeholders

• Cluster Infra

Definition of Done

• Fewer issues in the CAPI2MAPI conversion
• New options for metadata service configuration in MAPA

• Docs

• <Add docs requirements for this card>

• Testing

• <Explain testing that will be added>