Travis - Checkout the right K8s release and align on go version

[DanyC97]

Fixes #13121

cc @zacharysarah as per our last night slack chat

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

If they are not already assigned, you can assign the PR to them by writing /assign @ryanmcginnis 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

[DanyC97]

⚠️ examples needs attention

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit d86fd1e

https://deploy-preview-13122--kubernetes-io-master-staging.netlify.com

[netlify]

Deploy preview for kubernetes-io-master-staging ready!

Built with commit ba2890f

https://deploy-preview-13122--kubernetes-io-master-staging.netlify.com

[Bradamant3]

cc @tengqm -- Qiming, do you have ideas here? Seems related to fixes to the examples tests you've provided in the past. (See also #sig-docs Slack)

[tengqm]

Every release of k8s introduces some changes and/or refactoring that lead to test failure. The failure of this PR is expected and should be fixed. Need to examine the upstream code base to find out where the testing facility has been relocated.

[kbhawkey]

Hello. After some searching, here is one package change:
ValidationDaemonSet
ValidationDeployment
...
https://github.com/kubernetes/kubernetes/blob/56735065400825d03f8e8f1a546c7a7b5ba9c5fd/pkg/apis/apps/validation/validation.go

[kbhawkey]

@tengqm, I have not looked at the tests closely. Is this run for every build or only when an example changes. This area could use some documentation 👍

[DanyC97]

is this run for every build or only when an example changes.

@kbarnard10 is run on every build i think - see https://github.com/kubernetes/website/blob/master/.travis.yml#L23-L26

[tengqm]

@kbhawkey The test cases use to run on every build, before #11555 was merged. For all branches we maintain, we are supposed to use the correct version of go-lang and the correct version of upstream code for checking. This ensures that the examples we provide are usable for the version against which we have checked. I agree we should document this -- every time we create a dev-x.yz branch, we should adapt the travis CI job to use the latest versions of go-lang and upstream code. There could be changes that require revisions to the examples (thus the merits of the tests), e.g. beta version of resources got dropped, testing facility relocated etc.

[kbhawkey]

Thanks for the explanation @tengqm.

• Is there a way to automate this when a new docs dev branch is created? For example, this file would be updated on the docs 1.1.4 dev branch now?
• The changes for 1.13 are retroactive and would be evaluated with package/build updates in this patch?

[DanyC97]

@tengqm i see you created a new PR in which case i'll close this PR in favour of yours