-
Notifications
You must be signed in to change notification settings - Fork 318
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
feat: support IMDSv2 ( use aws-go-sdk-v2 ) #344
Conversation
Is anyone interested in merging this?? probably amazon will stop supporting the metadata api v1 sooner than we think... |
@Insidexa will you solve conflicts? |
@SCLogo yes, ~1w estimated time |
e87d5af
to
c7b3d6d
Compare
guys, I don't know, do we need to update IAM tests with regions ? because regions load from the AWS API |
Hi @jtblin , |
@atze234 that should be fixed with jtblin/kube2iam:dev now which supports |
Hi @jtblin, |
hi @atze234 , currently im try to install kube2iam 0.11.2 or latest in mi eks cluster , but I get several errors, could you tell me if my deployment is okay, I use it as a daemonset Daemonset:
and this is mi role kube2iamdemo in AWS: { any help or suggestion? |
Hi @jsebastianmal , |
Hi @atze234 , this is my errors in my kube2iam
this is an example to my IAM ROLE alfa-dev-eks-alfa-digital-dev-integrations
My app already set AWS Region src/main/resources/application.yml
and this is mi app logs:
|
Hi @atze234 , i found a bad config in my iam role , when i adjust this with the correctly policy in our Iam Node Group, kube2iam with IMDSV2 and my apps works fine. Thanks for your support. ;) |
What this PR does / why we need it:
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged)Special notes:
Checklist chart
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]