Set the STS client's region via IMDS for AssumeRoleWithWebIdentity #16647
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.
This should fix #16645
The dns-controller pods can have AWS_WEB_IDENTITY_TOKEN_FILE set when OIDC is set up. This causes the route53 client constructor to initialize an sts client internally and call AssumeRoleWithWebIdentity. This STS client needs a region configured, so we attempt to discover one via IMDS.
If IMDS is disabled on the dns-controller pod's node, the cluster operator will need to set AWS_DEFAULT_REGION as a workaround.