GCE e2e build/test passed for commit ed082389331eb4c7319f5eef40b6ae5a2554dc11.

• Test Results
• Build Log
• Test Artifacts
• Internal Jenkins Results

Remind me what this broke last time and why it's ok now.

@krousey #29001 has the gory history.

We will likely want to loop in @gmarek before we flip this switch too.

We're starting to enter into hard constraints due to the 1.5 goals of 5k nodes. Without this, we're simply going to start running out of ports.

This looks fine to me. I'll leave it to @gmarek for the final OK.

@timothysc - how urgent it is? We're running last scalability tests on master, so I'd rather wait a day or two until we're finished. Then we'll give it a try and see what happens.

@gmarek no rush.. hoping to flush out for 1.5

@timothysc - I'm fine with it, but please wait until 1.4 is out. Let's merge it next week.

sgtm.

So were all branched, unless someone objects I was going to apply today.

We have the TLS .NextProtos = ["h2"] thing right?

@smarterclayton not yet. I suppose we should block on #28742 then.

Can we not set that field also on Go 1.6? I thought it worked on both
versions, but was required for client cert on 1.7?

On Thu, Sep 22, 2016 at 12:51 PM, Timothy St. Clair <
[email protected]> wrote:

@smarterclayton https://github.com/smarterclayton not yet. I suppose we
should block on #28742
#28742 then.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#32231 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABG_pyCn4k2MEQWP27A5ygIHgbohOy47ks5qsrH7gaJpZM4J3Yal
.

You can set it on 1.6 too.

i'll update the pr.

@timothysc - we can merge this now, ping me when you'll update it for 1.6.

@gmarek ready.

Jenkins GCI Kubemark GCE e2e failed for commit 009f877. Full PR test history.

The magic incantation to run this job again is @k8s-bot kubemark gci e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

Jenkins GCI GKE smoke e2e failed for commit 009f877. Full PR test history.

The magic incantation to run this job again is @k8s-bot gci gke e2e test this. Please help us cut down flakes by linking to an open flake issue when you hit one in your PR.

LGTM

FYI @thockin

@k8s-bot test this [submit-queue is verifying that this PR is safe to merge]

Automatic merge from submit-queue