Skip to content
This repository has been archived by the owner on May 6, 2022. It is now read-only.

use GKE's default K8S version for Jenkins #1023

Merged
merged 1 commit into from
Jul 12, 2017

Conversation

kibbles-n-bytes
Copy link
Contributor

When 1.5.X was still the default for GKE, we needed special code when initializing the test cluster so that we'd get the latest 1.6.X version. This code assumed that:

  1. The latest cluster version would be no later than 1.6.X
  2. The default was earlier than 1.6.X

I just noticed that on the us-west1-a zone, 1.7.0 is the latest version and 1.6.4 is the default, meaning these two assumptions no longer hold, and Jenkins (which runs in the us-west1-b zone) is a ticking time bomb that is set to fail as soon as us-west1-b gets updated.

So for the time being, let's fix this to use the default version quickly (the default in us-west1-b is also 1.6.4), and then we can make a follow-up once time is on our side!

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 12, 2017
@jpeeler jpeeler added the LGTM1 label Jul 12, 2017
Copy link
Contributor

@arschles arschles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kibbles-n-bytes is it still possible to specify a GKE version? It'd be nice to do so forever, if possible, so that GKE changes don't necessarily break our build.

Copy link
Contributor

@MHBauer MHBauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hilarious, if irritating.

LGTM

@MHBauer MHBauer added the LGTM2 label Jul 12, 2017
@kibbles-n-bytes
Copy link
Contributor Author

kibbles-n-bytes commented Jul 12, 2017

@arschles Not easily, because GKE seems to get rid of earlier patch versions in favor of later patches of the same minor version. That's why that code was necessary in the first place back then. But we can still add something more robust to give us, for instance, "the latest 1.6 that exists", but that should be as a followup.

Copy link
Contributor

@arschles arschles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @kibbles-n-bytes. Can you make an issue for the follow-up?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. LGTM1 LGTM2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants