spring-cloud/spring-cloud-dataflow-acceptance-tests

Upgrade/Create Kubernetes cluster versions (GKE/PKS)

chrisjs opened this issue · 4 comments

  • Create two new PKS installations on GCP

  • Create one 1.12 and 1.13 Kubernetes cluster's on PKS installations (1.11 exists already)

  • Upgrade GKE clusters to 1.11, 1.12 & 1.13

  • Update env spreadsheet

Ha, I was just looking to create this issue. I'd suggest we try to sync with PKS n-2 releases as well, though this will mean additional sprawl...

yea its a bit cumbersome in general, touches a few places etc.

in terms of PKS, in GKE we can create whatever cluster versions they support. with PKS one instance can only run a single cluster version - all clusters in that instance stay at the same version or get upgraded together.

the toolsmith env doesn't appear to let you select a target k8s version, so if we want to have multiple k8s versions floating on PKS, looks like we would have to roll 2 of them on our own (and keep or upgrade the existing one).

The decision is to track n and upto n-2 releases in GKE and PKS.

Also, we will repave K8s clusters on-demand for each AT run as opposed to leaving the cluster intact until we revise to support the upstream cluster versions.

checkboxes checked 🔢