-
Notifications
You must be signed in to change notification settings - Fork 252
oss(credentials): support STS.Token in nodePublishSecretRef and rotation by republish #1591
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: master
Are you sure you want to change the base?
oss(credentials): support STS.Token in nodePublishSecretRef and rotation by republish #1591
Conversation
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
77d2b5d to
da50d2e
Compare
da50d2e to
5817fea
Compare
pkg/mounter/utils/filelock.go
Outdated
| } | ||
|
|
||
| // WriteFileWithLock safely writes data to file with locking | ||
| func WriteFileWithLock(path string, data []byte, perm os.FileMode) (done bool, err error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this lock secure the secret file update? If we write a new token to a separate file and then rename it, we wouldn't need locks?
9465193 to
c3b1c21
Compare
c3b1c21 to
4f91d33
Compare
6021061 to
51b3bcf
Compare
What type of PR is this?
/kind feature
What this PR does / why we need it:
requiredRepublishto true.kubectl create -n default secret generic oss-secret --from-literal='accessKeyId=<yourAccessKeyFromAssumeRole>' --from-literal='accessKeySecret=<yourAccessKeySecretFromAssumeRole>' --from-literal='securityToken=<yourSecurityTokenFromAssumeRole>' --from-literal='Expiration=2025-12-22T04:11:50Z'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.: