terraform-aws: variable driven ami selection

[mertcancam]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR enhances the AMI selection mechanism by making it variable-driven, enabling users to specify AMI filters directly through variables, thereby improving usability and customization. It aims to provide more flexibility to the users in selecting various AMIs for different distributions without altering the main Terraform files.

• Variables Driven AMI: Users can now specify ami_name_pattern, ami_owners and ami_virtualization_type through variables, enhancing configurability.
• Documentation Update: The README is updated to guide users on how to utilize this new variable-driven AMI selection method.

Which issue(s) this PR fixes:
Special notes for reviewers:

The variables.tf file is modified to accept ami_name_pattern, ami_owners and ami_virtualization_type as variables, ensuring that users can specify their preferred AMI without altering main files. This change is backward compatible as it keeps default values in line with the existing hardcoded configuration, ensuring no disruption for users who wish to continue using the existing method.

The README has been updated to reflect these changes and guide users on how to apply them. It provides examples and outlines the step-by-step method for specifying AMI attributes through variables.

Your feedback and insights regarding this implementation and its impact on the user experience would be highly valued.

Does this PR introduce a user-facing change?:

terraform-aws: variable driven ami selection (`ami_name_pattern`/`ami_virtualization_type`/`ami_owners`)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mertcancam / name: Mustafa Mertcan Çam (5411406, 2a8c39b, 3931dc2)

[k8s-ci-robot]

Welcome @mertcancam!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. 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/kubespray 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 @mertcancam. 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.

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/test-infra repository.

[yankay]

/ok-to-test

[floryut]

@mertcancam Thank you 👍

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: floryut, mertcancam

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

The pull request process is described here

Needs approval from an approver in each of these files:

• contrib/terraform/OWNERS [floryut]

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

[yankay]

Thanks @mertcancam
/lgtm