fix: cannot change the user's own avatar #4777
Conversation
f2c-ci-robot
bot
added
kind/bug
|
/milestone 2.11.x |
|
@LIlGG: once the present PR merges, I will cherry-pick it on top of release-2.10 in a new PR and assign it to you. In response to this:
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. |
Codecov Report
@@ Coverage Diff @@
## main #4777 +/- ##
=========================================
Coverage 61.50% 61.50%
Complexity 2798 2798
=========================================
Files 403 403
Lines 14772 14772
Branches 1029 1029
=========================================
Hits 9086 9086
Misses 5193 5193
Partials 493 493 |
|
/cherrypick release-2.10 |
|
@ruibaby: once the present PR merges, I will cherry-pick it on top of release-2.10 in a new PR and assign it to you. In response to this:
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. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JohnNiang 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 |
f2c-ci-robot
bot
added
the
approved
|
@LIlGG: new pull request created: #4778 In response to this:
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. |
This is an automated cherry-pick of #4777 /assign LIlGG ```release-note 解决无用户管理权限的用户无法上传头像的问题 ```
What type of PR is this?
/kind bug
What this PR does / why we need it:
当前用户上传头像时的接口中名字应该是
-而不是具体的 metadata name。How to test it?
使用无用户管理权限的用户登录，查看是否能上传头像。
Which issue(s) this PR fixes:
Fixes #4776
Does this PR introduce a user-facing change?