IMDSv2 release?

[bbegw]

Hi, thanks for all the work on this project.

I see that this PR for IMDSv2 support has been merged, but there's no release which includes it (seems to only be in the dev/snapshot tag).

Is there a plan to release this change as a tagged version? Thank you!

[act-mreeves]

@jtblin thanks for this great project. Do you think we could cut a release soon with this ImdsV2 support?

[jtblin]

Sorry about the delay, it was a mess with CircleCI and pushing to Docker. It's fixed now but I don't think I'll be able to push 0.12.0, the workaround is to use the git hash: docker pull jtblin/kube2iam:c23584c instead.

I've also upgraded Go and Alpine so you can use 0.13.0 and latest.

[Tesseract99]

I used the jtblin/kube2iam:c23584c image, but I get this error in kube2iam pod when an application pod tries to go through kube2iam for accessing its IAM role.

level=error msg="Error assuming role operation error EC2: DescribeRegions, failed to resolve service endpoint, an AWS region is required, but was not found"

This error is resolved when I set the AWS_DEFAULT_REGION env variable in both the kube2iam and the application pods.

This is a v1.32.6 KOps Kubernetes cluster.

[dgokcin]

We had the same problem. @Tesseract99 did you have to add the AWS_DEFAULT_REGION env var to all application pods that are running in your cluster or only the ones that used kube2iam through an annotation?