✨ Add node auto repair configuration for EKS managed node groups

[afarbos]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR adds support for node auto repair configuration in EKS managed node groups. Node auto repair is a feature that allows EKS to automatically repair unhealthy nodes by replacing them, helping maintain cluster health and availability.

https://aws.amazon.com/about-aws/whats-new/2024/12/node-health-monitoring-auto-repair-amazon-eks/

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

• API Types: Added NodeRepairConfig field to AWSManagedMachinePoolSpec with an enabled boolean field
• EKS Service: Integrated node repair configuration into node group creation and update logic
• Converters: Added NodegroupRepairConfigToSDK and NodegroupRepairConfigFromSDK functions
• Tests: Added comprehensive unit tests for the new converter functions

Checklist:

• squashed commits
• includes documentation
• includes emoji in title
• adds unit tests
• adds or updates e2e tests

Release note:

Added support for configuring node auto repair functionality in EKS managed node groups

[k8s-ci-robot]

Hi @afarbos. 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-sigs/prow repository.

[serngawy]

@afarbos rebase is required for the PR

[afarbos]

@afarbos rebase is required for the PR

rebased

[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 ask for approval from andidog. For more information see the Code Review Process.

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

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

[afarbos]

I also tried to add a e2e test here after I saw them. I am not sure how to run them here.

[AndiDog]

/ok-to-test
/test pull-cluster-api-provider-aws-e2e-eks
/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: e9654264f42f3d4950b4533ce50f01074db3c139

[afarbos]

/retest

[afarbos]

/retest

[afarbos]

/retest

[AndiDog]

/lgtm

On to @kubernetes-sigs/cluster-api-provider-aws-maintainers for a second pair of eyes and approval

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: e5dbb561cff2dffb3e1dafcb598d58a9fe81d02e

[damdo]

/assign @nrb @richardcase @dlipovetsky @Ankitasw

[AndiDog]

/test pull-cluster-api-provider-aws-e2e-eks

[k8s-ci-robot]

@afarbos: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-aws-e2e-eks	f2c01bf	link	false	/test pull-cluster-api-provider-aws-e2e-eks

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.