This repository has been archived by the owner on Jul 27, 2022. It is now read-only.
feat: Add support for WebIdentityProvider (EKS) #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We used to fallback to
InstanceMetadataProviderif no explicit credentials are supplied.This is very useful because it makes it easy to autoconfigure credentials when running workload on k8s.
AWS is moving away from InstanceMetadataProvider on K8s, and requires the
WebIdentityProviderwhen running onEKS.This PR adds support for
WebIdentityProviderin the same vein as it supportedInstanceMetadataProvider, namely as a fallback when no other explicit auth methods is provided.