-
Notifications
You must be signed in to change notification settings - Fork 795
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
Not able to get IAM credentials with IMDSv1 #4896
Comments
3 tasks
@friedrichg I am curious about the use of disabling the IMDv2's session API? The reason I am asking is I want to make a case to have the minio revert/fix the bug fix :) |
kube2iam does not support the session API jtblin/kube2iam#282 There is no other reason. I also think the bugfix in minio-go is probably correct for minio but not for AWS. |
@friedrichg this is resolved with the PR right? |
yes, Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Cortex is not able get IAM credentials with IMDSv1 auth
To Reproduce
Steps to reproduce the behavior:
Click to expand!
level=error ts=2022-10-05T20:31:27.540353246Z caller=blocks_cleaner.go:155 component=cleaner msg="failed to run blocks cleanup and maintenance" err="failed to discover users from bucket: Access Denied"
Expected behavior
it should continue without problem
Environment:
Additional Context
It works in the previous commit f550642
Previous
cortex/vendor/github.com/minio/minio-go/v7/pkg/credentials/iam_aws.go
Lines 291 to 298 in f550642
Current
cortex/vendor/github.com/minio/minio-go/v7/pkg/credentials/iam_aws.go
Lines 291 to 301 in e2cfc51
This bugfix minio/minio-go#1682 is most likely the culprit
The text was updated successfully, but these errors were encountered: