add support for new aws partitions in credential provider #981
Conversation
k8s-ci-robot
added
release-note-none
|
This issue is currently awaiting triage. If cloud-provider-aws contributors determine this is a relevant issue, they will accept it by applying the The 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. |
k8s-ci-robot
added
the
needs-triage
k8s-ci-robot
added
the
size/S
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims 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 |
k8s-ci-robot
added
the
approved
|
/test pull-cloud-provider-aws-e2e-kubetest2 |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
…ream-release-1.27 Automated cherry pick of #981: add support for new aws partitions in credential provider
…ream-release-1.28 Automated cherry pick of #981: add support for new aws partitions in credential provider
…ream-release-1.29 Automated cherry pick of #981: add support for new aws partitions in credential provider
…ream-release-1.30 Automated cherry pick of #981: add support for new aws partitions in credential provider
What type of PR is this?
/kind feature
What this PR does / why we need it:
Allow credential provider to recognize new aws partitions.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: