[EKS] [request]: Provide Ability to Set Hop Limit in NodeClass Resource

[bdumford-OM1]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Tell us about your request
I would like the NodeClass resource from api version eks.amazonaws.com/v1 to be able to set MetaDataOptions, especially the hop limit (httpPutResponseHopLimit). This NodeClass resource is the only one that Auto Mode is able to use.

Which service(s) is this request for?
EKS

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
I am currently blocked from using Auto Mode with an application that requires I use pods that need access to the instance metadata. There is no way to configure the hop limit to 2 or greater in the NodeClass resource to allow access. I am able to do this in Karpenter's EC2NodeClass.

Are you currently working around this issue?
I cannot currently work around this issue.

Additional context
None

Attachments
None

[lucdew]

It is probably the reason why we cannot use the aws fluentbit filter and thus augment the logs with AWS metadata.

On Karpenter it works but in AWS EKS auto-mode the retrieval of the token for the metada service v2 fails.

The following request from the fluentbit (2.31) pod times-out:
curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"

I checked the EC2 instance started by EKS auto-mode and imdsv2 is required.