Feature/test invite (#528)

[mini-bot]

This is an automated cherry-pick of #528

What problem does this PR solve?

Issue Number: close #526

Problem Summary:

What is changed and how it works?

Proposal: xxx

What's Changed:

How it Works:

Check List

Tests

• [ ] Unit test
• [ ] Integration test
• [ ] Manual test (add detailed scripts or steps below)
• [ ] No code

Side effects

• [ ] Performance regression: Consumes more CPU
• [ ] Performance regression: Consumes more Memory
• [ ] Breaking backward compatibility

Documentation

• [ ] Affects user behaviors
• [ ] Contains syntax changes
• [ ] Contains variable changes
• [ ] Contains experimental features
• [ ] Changes MySQL compatibility

Release note

Please add a release note, or a 'None' if it is not needed.

[mini-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment. After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review. Reviewer can cancel approval by submitting a request changes review.

[wuhuizuo]

/cherry-pick-invite

[wuhuizuo]

/cherry-pick-invite

[wuhuizuo]

/cherry-pick-invite

[wuhuizuo]

/cherry-pick-invite

[wuhuizuo]

/cherry-pick-invite

[mini-bot]

@wuhuizuo Please accept the invitation then you can push to the cherry-pick pull requests. Comment with "/cherry-pick-invite" if the invitation is expired. https://github.com/mini-bot/test-dev/invitations

[zuo-bot-1]

@mini-bot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
prow_debug	850551002896e8b75f15543b6d5e75bde0f507cc	link	true	/test prow_debug

Full PR test history.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[ti-chi-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Send feedback to sig-community-infra or Mini256. /lifecycle stale

[ti-chi-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. If this issue is safe to close now please do so with /close. Send feedback to sig-community-infra or Mini256. /lifecycle rotten