Fix generating presigned URL for K8s authentication #7487
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
With
[email protected], API server requests containing URLs presigned bysts.PresignClientfail with anUnauthorizederror.[email protected]adds an extra headeramz-sdk-requestto the generated request, but this header is not allow-listed byaws-iam-authenticatorserver running on the control plane. This is likely due to this change which reorders the middleware operations to executeRetryMetricsHeaderbeforeSigning.This changelist removes the
RetryMetricsHeadermiddleware from the stack when constructingsts.PresignClient.This functionality is part of
aws-sdk-go-v2and is therefore not covered by unit tests.Fixes #7486
Checklist
README.md, or theuserdocsdirectory)area/nodegroup) and kind (e.g.kind/improvement)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯