fix: handle missing secret-userdata.txt for MachinePool/ASG nodes

[andrejbella]

Change description

Fixes #1917 by handling MachinePool/ASG nodes where userdata is passed directly
via EC2 metadata instead of being written to /etc/secret-userdata.txt by the
boothook. Previously the datasource would fail because it expected this file to exist.
The bug was introduced with this commit

Related issues

• Fixes #

Additional context

This may not be the most ideal fix as we are essentially just guessing that the reason the file is missing is the deployment type.
Suggestions are welcome

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mboersma for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @andrejbella!

It looks like this is your first PR to kubernetes-sigs/image-builder 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/image-builder has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @andrejbella. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[richardcase]

/ok-to-test

[richardcase]

Thanks for this @andrejbella .

Could you confirm what testing you have done with this change? Have you built your own AMI and tested with CAPA?

[andrejbella]

@richardcase I have built the custom AMI with this change and deployed both MD and MP clusters. Both deployed ok. Without this, only the MD succeeded

CAPA: v2.10.0
CAPI: v1.12.2