Seems like kubectl v1.9.0 was installed on those nodes. Here is the puppet script I found that used to download and install kubectl on beam-jenkins. https://github.com/apache/infrastructure-puppet/blob/95aed4f4f7cdce79a1f0fc8b1e581f13fedf63ff/modules/build_slaves/manifests/kube.pp
On Thu, May 24, 2018 at 10:18 AM Alan Myrvold <amyrv...@google.com> wrote: > I can update the version of the io-datastores cluster master and node > pools. > I don't have access to the kubectl version on the executors ... I can ask > around for that. > > On Wed, May 23, 2018 at 4:59 AM Kamil Szewczyk <szewi...@gmail.com> wrote: > >> Dear Beam Devs, >> >> we are using kubernetes to on demand create/tear down resources for >> performance testing. It is done automatically by Jenkins jobs using >> PerfKit. On 20th of May, there was a blog post about security issues in >> kubernetes >> https://cloud.google.com/kubernetes-engine/docs/security-bulletins and >> we should upgrade it to the latest version of the main branch. As far as I >> know in apache-beam-testing, we are now using kubernetes cluster with >> engine version 1.8, can we update it to version 1.9(1.9.7-gke.1)? >> We are missing some new cool features introduced in kubernetes 1.9 like >> StatefulSets which I would like to use to setup HDFS large cluster for >> performance testing, I have already submitted PR for that. My findings are >> described in this two JIRA issues: >> - https://issues.apache.org/jira/browse/BEAM-4362 >> - https://issues.apache.org/jira/browse/BEAM-4390 >> >> Who is in charge of Google Cloud Platform (have admin access) and can >> help with that? >> >> >>
