-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
changed tagsha to recent builds #10001
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ok-to-test
after kubernetes/k8s.io#5333 (comment) has been merged. we can change and update the image sha in this PR? |
Yes. That was plan.
…On Sat, 27 May, 2023, 5:47 pm Jintao Zhang, ***@***.***> wrote:
after kubernetes/k8s.io#5333 (comment)
<kubernetes/k8s.io#5333 (comment)> has
been merged. we can change and update the image sha in this PR?
—
Reply to this email directly, view it on GitHub
<#10001 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABGZVWVE54BEE6RJ4PEPASLXIHWFHANCNFSM6AAAAAAYREDYT4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
d40ce94
to
c7c7aad
Compare
@tao12345666333 echoserver also changed so now waiting for CI |
@tao12345666333 @strongjz CI passed |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: longwuyuan, strongjz 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 |
What this PR does / why we need it:
Types of changes
Which issue/s this PR fixes
How Has This Been Tested?
Checklist:
cc @tao12345666333 @strongjz @rikatz
/triage accepted
/kind bug
/priority important-soon