Support EKS Hybrid Nodes

[TylerGillson]

/kind feature

Describe the solution you'd like

Now that Amazon EKS Hybrid Nodes are GA'd, CAPA should support all hybrid-related fields during EKS cluster provisioning.

Anything else you would like to add:

• The following new fields in the Amazon EKS CreateCluster payload must be supported.
• They're already available via aws-sdk-go-v2.

Environment:

• Cluster-api-provider-aws version: N/A
• Kubernetes version: (use kubectl version): N/A
• OS (e.g. from /etc/os-release): N/A

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[punkwalker]

I will be working this but waiting on some updates on #2225

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[vrabbi]

Any updates around this? We would really love to have this functionality

[punkwalker]

Any updates around this? We would really love to have this functionality

EKS packages are migrated to AWS SDK V2 #5498.

We would have hybrid node functionality soon.

[punkwalker]

/assign punkwalker

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[csplinter]

/remove-lifecycle rotten

[vrabbi]

Any updates?