aws / aws/containers-roadmap

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

Open
#2,498 13 comments 36 reactions 0 assignees View on GitHub
EKS EKS Auto Mode Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) 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](https://karpenter.sh/docs/concepts/nodeclasses/).

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

**Additional context**
None

**Attachments**
None

Contributor guide

Open the contributing guide

Research direction

Start with the NodeClass resource in api version eks.amazonaws.com/v1 and compare its available settings with Karpenter's EC2NodeClass documentation linked in the issue. Confirm how MetaDataOptions and httpPutResponseHopLimit should be represented for EKS Auto Mode; done means the NodeClass can configure a hop limit of 2 or greater for pods needing instance metadata access.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.