Google Container Engine 2017-08-07 release

[Tim Allclair]

August 7, 2017

• Kubernetes v1.7.3 is available for new clusters and opt-in master upgrades.

• Kubernetes v1.6.8 is available for new clusters and opt-in master upgrades.

• Cluster masters running Kubernetes version v1.6.6 or older will be upgraded to v1.6.7 according to the following schedule:

  • 2017-08-08: europe-west2-a us-east1-d
  • 2017-08-09: asia-east1-a asia-northeast1-a asia-southeast1-a australia-southeast1-a europe-west1-c europe-west3-a us-central1-b us-east4-b us-west1-a
  • 2017-08-10: asia-east1-c asia-northeast1-b asia-southeast1-b australia-southeast1-b europe-west1-b europe-west2-b europe-west3-b us-central1-f us-east1-c us-east4-c us-west1-b
  • 2017-08-11: asia-east1-b asia-northeast1-c australia-southeast1-c europe-west1-d europe-west2-c europe-west3-c us-central1-a us-central1-c us-east1-b us-east4-a us-west1-c

• Node pools can now be created with an initial node count of 0.

• Cloud monitoring can only be enabled in clusters that have monitoring scope enabled in all node pools.

• Known Issues upgrading to v1.6.7:

• Kubernetes 1.6.7 includes version 0.9.5 of the GCP Ingress Controller. This version contains a fix for a bug that caused the controller to incorrectly synchronize GCP URL Maps. Changes to the ingress resource may not have caused the GCP URL Map to update. Using the fixed controller will ensure maps reflect the host and path rules. To avoid potential disruption, validate that all ingress objects contain the desired host or pathrules.

https://cloud.google.com/container-engine/release-notes#august_7_2017