Force kube 1.14 golang.org/x/net

[enj]

This allows the http2 code to respect "Connection" == "close" to mean sending a GOAWAY and tearing down the TCP connection.

Signed-off-by: Monis Khan [email protected]

@openshift/sig-auth @openshift/sig-master

@smarterclayton I believe you said you wanted this to be bumped to latest?

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: enj
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: pweil-

If they are not already assigned, you can assign the PR to them by writing /assign @pweil- in a comment when ready.

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:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[smarterclayton]

Bumped to kube, preferably.

[enj]

Bumped to kube, preferably.

Set it to release-branch.go1.12 to match kube 1.14

[deads2k]

good thing we all love sally

[deads2k]

So uh, for those of us in the peanut gallery, is there a thing you need to do to trigger this? You definitely need to at least try to make test proving you destroy these connections and if you have code to add to make this bump effective, you need that too. I'm not seeing a good reason to do this bump yet.

[openshift-ci-robot]

@enj: The following tests failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
ci/prow/unit	95efa7d	link	/test unit
ci/prow/e2e-aws-serial	95efa7d	link	/test e2e-aws-serial

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.

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/test-infra repository. I understand the commands that are listed here.

[tnozicka]

There were some issues upstream in net package, not sure if we hook up the one from golang or the experimental to those particular places. (e.g. golang/go#27044)

This would also mean we take pretty significant change from upstream that is compiled and tested with different go version. And there are regressions if we consider bumping to go1.12 - kubernetes/kubernetes#75833 kubernetes/kubernetes#75837

[enj]

#22529