-
Notifications
You must be signed in to change notification settings - Fork 289
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
*: prompt k8s.io/api version #11866
*: prompt k8s.io/api version #11866
Conversation
/test verify |
/retest |
1 similar comment
/retest |
/test cdc-integration-mysql-test |
/test dm-integration-test |
/test cdc-integration-pulsar-test |
/test cdc-integration-pulsar-test |
/test cdc-integration-kafka-test |
62c6656
to
75691e2
Compare
/test verify |
/test engine-integration-test |
/retest |
/test cdc-integration-pulsar-test |
/test cdc-integration-kafka-test |
/test cdc-integration-pulsar-test |
/test cdc-integration-mysql-test |
75691e2
to
f4b8b0c
Compare
[LGTM Timeline notifier]Timeline:
|
/retest |
3 similar comments
/retest |
/retest |
/retest |
/test cdc-integration-storage-test |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
In response to a cherrypick label: new pull request created to branch |
@wlwilliamx: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
What problem does this PR solve?
Issue Number: close #11865
k8s.io/api
has risks of some security issue at current v0.28.x version.What is changed and how it works?
Prompt the version to v0.29.11.
Check List
Tests
Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note