fix: update search time service keywords #198
Conversation
Signed-off-by: qinyer <qy913726062@gmail.com>
|
@qinyer: 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
size/XS
Codecov Report
@@ Coverage Diff @@
## master #198 +/- ##
=======================================
Coverage 12.99% 12.99%
=======================================
Files 105 105
Lines 16034 16034
=======================================
Hits 2084 2084
Misses 13699 13699
Partials 251 251
|
|
/lgtm |
|
LGTM label has been added. Git tree hash: 4d928d3d3beb4cc95d2b56da2ba4778cc5a88d5c
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qinyer, x893675 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 |
kubeclipper-bot
added
the
approved
|
/cherrypick release-1.1 |
|
@x893675: once the present PR merges, I will cherry-pick it on top of release-1.1 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. |
|
@x893675: new pull request created: #199 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. |
Signed-off-by: qinyer qy913726062@gmail.com
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #196
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: