-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature] Make HttpPutResponseHopLimit configurable #7665
Comments
Hi @nikita-b , may I ask a couple questions for clarification:
eksctl/pkg/cfn/builder/nodegroup.go Lines 534 to 547 in 76902cd
|
Hello @TiberiuGC,
We use self-managed nodes.
Nope, I want to have access to AWS metadata from containers that with Docker-in-Docker. Because in this case we have |
+1. I would like to be able to specify the hopLimit in my clusterConfig so I can avoid having to create launch templates prior to creating the cluster just so I can set the hop limit = 2. |
What feature/behavior/change do you want?
We need to have HttpPutResponseHopLimit == 3
Why do you want this feature?
We use DIND in our Kubernetes cluster (it's cluster for Gitlab agents) and we can't disable IMDSv1 because hop from DIND container is 3
The text was updated successfully, but these errors were encountered: