oss(credentials): support standard keys accessKeyId and accessKeySecret
#1565
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
k8s-ci-robot
added
the
kind/feature
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AlbeeSo 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
approved
AlbeeSo
force-pushed
the
feat/compatible-standard-credientials-fields
branch
from
230eaad to
05af70f
Compare
AlbeeSo
changed the title
accessKeyId and accessKeySecret
AlbeeSo
force-pushed
the
feat/compatible-standard-credientials-fields
branch
2 times, most recently
from
d0fdf2b to
502e0d2
Compare
AlbeeSo
force-pushed
the
feat/compatible-standard-credientials-fields
branch
from
502e0d2 to
1177d1d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
AccessKeyIdandAccessKeySecretare the more common fields for credentials.But still prioritizes obtaining the credentials from
AkIDandAkSecretto keep compatibility.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: