-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Kube 1.4 cherry picks #11709
Kube 1.4 cherry picks #11709
Conversation
[test] |
[test] #10228 |
Evaluated for origin test up to b4597a4 |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10956/) (Base Commit: 16306a6) |
1 similar comment
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10956/) (Base Commit: 16306a6) |
That additional commit LGTM. |
[merge] |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/10956/) (Image: devenv-rhel7_5300) |
Evaluated for origin merge up to b4597a4 |
It looks like we dropped the etcd3 perf changes... so, I would pretty much never recommend to go clientv3 then. /cc @mffiedler |
@timothysc dropped as in they used to be there and we accidentally removed them, or we didn't get around to pulling them in? |
@smarterclayton do you want upstream 35205 in? |
Both of the doubtful PRs are:
and I decided not to include them by default due to possible complications at this point in time. I'm leaving that decision to @smarterclayton about both of them. |
Pretty sure we need 35205 - is it a hard patch? On Nov 2, 2016, at 3:50 PM, Maciej Szulik notifications@github.com wrote: Both of the doubtful PRs are:
and I decided not to include them by default due to possible complications — |
Not sure if hard, but a big one. I'll give it a shot on my way to Brno. |
xref #11642
I've added a drop commit to fix the e2es panicking. We'll see how it goes.