-
Notifications
You must be signed in to change notification settings - Fork 603
✨ Add support for profile selection in clusterawsadm bootstrap credentials encode-as-profile #5495
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
base: main
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @v47! |
Hi @v47. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
…als encode-as-profile
77f5c56
to
95c8f7f
Compare
What type of PR is this?
/kind feature
What this PR does / why we need it:
Currently, clusterawsadm bootstrap credentials encode-as-profile only works with the default AWS profile. This limitation makes it inconvenient to use the tool in environments that rely on multiple named profiles, reducing its effectiveness for generating AWS_B64ENCODED_CREDENTIALS.
Special notes for your reviewer:
Checklist:
Release note: