Bumped gRPC version to 1.3.0#51154
Conversation
|
Hi @RenaudWasTaken. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with I understand the commands that are listed here. DetailsInstructions 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. I understand the commands that are listed here. |
|
/ok-to-test |
5c82eb0 to
c56ec71
Compare
|
Forgot to update the staging Godeps that's done now |
| { | ||
| "ImportPath": "github.com/gogo/protobuf/gogoproto", | ||
| "Comment": "v0.4-3-gc0656edd", | ||
| "Comment": "v0.4-3-gc0656ed", |
There was a problem hiding this comment.
What version is this? Is there no official release tag that we can use?
There was a problem hiding this comment.
I agree that this is something that should be addressed however I don't believe this is the scope of this PR as neither this or the previous one changed the commit number.
There was a problem hiding this comment.
There is an actual release - https://github.com/gogo/protobuf/releases/tag/v0.4
I hope a similar release would be available for other dependencies.
I'd like to avoid vendoring in HEAD of dependencies.
@wojtek-t @shyamjvs since you are experts in this area, can you weigh in?
There was a problem hiding this comment.
@vishh I'd like to avoid revendoring anything else than gRPC and it's dependecies (x/net and x/text).
I really think that doing so is outside the scope of this PR and would need to go through the whole re-testing on a 100 node cluster.
Let's keep the changes to the minimum to avoid breaking anything else :)
There was a problem hiding this comment.
I'm no expert here, but I'm seeing quite some packages in the file that don't seem to be from standard releases (e.g docker/engine-api, coreos/pkg). Apparently even the go-restful pkg.
IMO allowing only releases could become a serious limitation wrt feature velocity (i.e. wait for an upstream release before using it in your feature).
cc @thockin - the godep god :)
|
@shyamjvs can you do a stress test on this branch to confirm everything is OK? |
|
@RenaudWasTaken I'll test it on 100-node cluster - Can you please rebase before that? |
c56ec71 to
14450dd
Compare
|
@shyamjvs should be good now :) |
|
I'm on it. |
|
/retest |
|
/lgtm I tested it locally on 100-node cluster and it works now: |
|
Thanks for fixing. |
|
/retest |
|
/approve |
|
/retest |
14450dd to
1daaeb3
Compare
|
Forgot once again to run |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RenaudWasTaken, shyamjvs, wojtek-t Associated issue: 695 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
|
/test all [submit-queue is verifying that this PR is safe to merge] |
|
Automatic merge from submit-queue (batch tested with PRs 51193, 51154, 42689, 51189, 51200) |
|
@RenaudWasTaken: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. I understand the commands that are listed here. |
What this PR does / why we need it:
This PR bumps down the version of the vendored version of gRPC from v1.5.1 to v1.3.0
This is needed as part of the Device Plugin API where we expect client and server to use the Keep alive feature in order to detect an error.
Unfortunately I had to also bump the version of
golang.org/x/textandgolang.org/x/net.Which issue this PR fixes: fixes #51099
Which was caused by my previous PR updating to 1.5.1
Special notes for your reviewer:
@vishh @jiayingz @shyamjvs
Release note: