Support IAM Roles for Service Accounts in EKS #60
Conversation
This file contains hidden or 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
cosmo0920
reviewed
Oct 28, 2019
|
@cosmo0920 Thanks for the review. I will write an example configuration in the README. |
|
I wrote an example configuration in the README. |
cosmo0920
approved these changes
Oct 29, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hello, I'm using your plugin on EKS.
AWS has released the new feature for EKS. When I was migrating to this, I found something that didn't work with your plugin.
This feature uses OIDC JSON web token so
Aws::AssumeRoleCredentialscould not get IAM Roles...So I modified your plugin to use
Aws::AssumeRoleWebIdentityCredentialsif web token exists.