-
Notifications
You must be signed in to change notification settings - Fork 25
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
feat: container credential provider support auth token #107
Conversation
Luacheck Report39 tests 0 ✅ 0s ⏱️ For more details on these failures, see this check. Results for commit 132762f. ♻️ This comment has been updated with latest results. |
Here @Tieske I added back the token environment variable and remove useless comments/TODOs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, but needs a rebase
cf75f2c
to
8ef9c77
Compare
rebased |
Summary
This PR adds support for using authorization token in Container Credential Provider. Container Credential Provider uses two environment variables for the auth token content:
AWS_CONTAINER_AUTHORIZATION_TOKEN
(for token value) andAWS_CONTAINER_AUTHORIZATION_TOKEN_FILE
(for a file path that stores token value). See https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html. If one of the token env vars exists, the token value will be used asAuthorization
header value when requesting credential provider URI.By adding support for auth token in Container Credential Provider, we can support the latest "Pod Identity" IAM Auth method in AWS EKS. See How EKS Pod Identity works
Reference:
https://github.com/aws/aws-sdk-js/blob/3276faf83e32dfea637797c66a73431affe54e64/lib/credentials/remote_credentials.js#L118C3-L118C18
https://konghq.atlassian.net/browse/KAG-3424