fix: fix bugs #255
fix: fix bugs #255
Conversation
|
@moweiwei: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
kubeclipper-bot
added
dco-signoff: yes
do-not-merge/release-note-label-needed
approved
1. container registry display 2. enable reset cluster when status is Updating 3. disable backup for rancher cluster Signed-off-by: moweiwei <mo.weiwei@99cloud.net>
|
/cherrypick release-1.3 |
|
@moweiwei: once the present PR merges, I will cherry-pick it on top of release-1.3 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lysign, moweiwei 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 |
|
LGTM label has been added. Git tree hash: ecc28153fa051160b4ee97f99c3aa2f55a47ce68
|
|
@moweiwei: new pull request created: #256 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. |
1. container registry display 2. enable reset cluster when status is Updating 3. disable backup for rancher cluster Signed-off-by: moweiwei <mo.weiwei@99cloud.net> Signed-off-by: moweiwei <mo.weiwei@99cloud.net>
Signed-off-by: moweiwei mo.weiwei@99cloud.net
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: