-
Notifications
You must be signed in to change notification settings - Fork 647
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
Unable to authenticate using node role #1866
Comments
@coufalja - was there any progress on the issue? I believe that the changes introduced in #1682 are causing the issue where if IMDSv2 is disabled, an error is raised. whereas earlier the same error was ignored. this is preventing the use of IMDSv1 as well - as the request to generate role creds is made afterwards. |
I will check on the fix. |
I ended up doing the fix in Tempo itself grafana/tempo#2760 as I thought this was an intended behavior. |
@harshavardhana - incase of IMDSv2 is disabled. we are seeing an error thrown: I believe #1682 might've introduced this issue |
This is not clearly intended behavior, will fix it. |
@harshavardhana - let me know if I can help with the fix, will create a PR. |
@harshavardhana - LGTM |
Cause and effect:
During the investigation of grafana/tempo#2743 I was able to track down the problem to specific commits in mino-go #1626 and #1682.
Those two together causes us not being able to authenticate, and subsequent Tempo error.
If that is expected behavior (as it seems according to this Cortex commit cortexproject/cortex#4897) the issue lies in the usage of the library.
The text was updated successfully, but these errors were encountered: