-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Alicloud: allow use RAM role for OSS client #8025
Conversation
Hi @bittopaz. Thanks for your PR. I'm waiting for a kubernetes 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/test-infra repository. |
/ok-to-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bittopaz, zetaab 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 |
…-upstream-release-1.17 Automated cherry pick of #8025: Alicloud: allow use RAM role for OSS client
…-upstream-release-1.16 Automated cherry pick of #8025: Alicloud: allow use RAM role for OSS client
This is part of #4127.
This is the first step to gradually move from environment variables ACCESS KEY and SECRET to instance RAM role (known as IAM role in EC2).
This is also related with kopeio/etcd-manager#269. After this PR gets merged, I will try make another separate PR to update the kops dependency to latest in etcd-manager.
Then kopeio/etcd-manager#269 can be merged.