Bump golang versions to 1.7.5

[cblecker]

What this PR does / why we need it: While #41636 might not make it in until 1.7, this would bump current golang versions from 1.7.4 to 1.7.5 to integrate the fixes from that patch version. This would include, among other things, a fix to ensure cross-built binaries for darwin don't have certificate validation errors (golang/go#18688)

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): none

Special notes for your reviewer:

Release note:

Upgrade golang versions to 1.7.5

[k8s-ci-robot]

Hi @cblecker. 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 @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

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.

[k8s-reviewable]

This change is 

[ixdy]

LGTM. building cross image now, will push and then trigger tests.

[ixdy]

not essential, but maybe update this comment too for consistency?

[cblecker]

Fixed!

[ixdy]

gcr.io/google_containers/kube-cross:v1.7.5-1 pushed.
@k8s-bot ok to test
/lgtm

[ixdy]

/approve

[ixdy]

@k8s-bot test this

[mikedanese]

/approve

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

The following people have approved this PR: cblecker, ixdy, mikedanese

Needs approval from an approver in each of these OWNERS Files:

• build/OWNERS [ixdy,mikedanese]
• cluster/OWNERS [mikedanese]
• test/OWNERS [ixdy,mikedanese]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[ixdy]

@k8s-bot cross build this

[cblecker]

These don't look related to this PR, but it seems the queue is currently blocked.

[cblecker]

Looks like the queue might be running again, so let's give this a shot:
@k8s-bot cvm gke e2e test this
@k8s-bot gci gke e2e test this
@k8s-bot non-cri e2e test this
@k8s-bot cvm gce e2e test this

[cblecker]

@k8s-bot non-cri e2e test this

[cblecker]

@ixdy Question: Is this worth cherrypicking back to release-1.5, as 1.5 is using go1.7.4 as well?

[ixdy]

@cblecker yeah, seems like a good idea, since 1.6 won't be released for a while yet. cc @mwielgus

[cblecker]

@saad-ali FYI :)

[cblecker]

Also, maybe a dumb question as I'm relatively new around these parts..
I know release-1.6 recently opened up ahead of Monday's code freeze.. does this also need a cherrypick against that? Or will it be batched in before Monday?

[ixdy]

There will be regular fast-forwards of the release-1.6 branch from master.
Starting Monday, if this PR hasn't yet merged, we'll need to add the 1.6 milestone tag.

[cblecker]

Got it! Thank you!

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 41812, 41665, 40007, 41281, 41771)

[cblecker]

@ixdy @saad-ali: As this is now in master, is there anything else I should do to help it get picked into release-1.5? (I haven't done this before, so thanks for your patience)

[ixdy]

@cblecker run the hack/cherry_pick_pull.sh script: https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md

[cblecker]

Awesome, thank you! I've opened #42005 using that script.

Note: During conflict resolution, I removed a couple of the changes that were in this PR as there are parts of 1.5 that are still on go 1.6, and that is a much bigger jump. The cross-build image though was 1.7.4, so that's the big one.

[k8s-cherrypick-bot]

Commit found in the "release-1.5" branch appears to be this PR. Removing the "cherrypick-candidate" label. If this is an error find help to get your PR picked.