-
Notifications
You must be signed in to change notification settings - Fork 297
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
Use session token in aws authentication #9419
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9419 +/- ##
==========================================
+ Coverage 69.45% 69.47% +0.02%
==========================================
Files 672 672
Lines 49357 49381 +24
==========================================
+ Hits 34280 34307 +27
+ Misses 13290 13288 -2
+ Partials 1787 1786 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
13c9758
to
52d677d
Compare
52d677d
to
991ea97
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vivek-koppuru The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-0.22 |
@sp1999: new pull request created: #9467 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-0.21 |
@sp1999: new pull request created: #9468 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Issue #, if available:
https://github.com/aws/eks-anywhere-internal/issues/2650
#9177
Description of changes:
As part of migrating from using long term credentials in e2e test, I am making changes here to use session token and propogate it to secrets which will be used by curated packages.
Testing (if applicable):
Created a cluster and verified that secrets created has the session token if available. Tested the normal case where there is no session token
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.