Google Container Engine 2017-07-18 release

[CJ Cullen]

July 18, 2017

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

• Cluster masters running Kubernetes version v1.7.0 will be upgraded to v1.7.1 according to the following schedule:

  • 2017-07-18: us-east1-d europe-west2-a
  • 2017-07-19: europe-west1-c us-central1-b us-west1-a asia-east1-a asia-northeast1-a asia-southeast1-a us-east4-b australia-southeast1-a
  • 2017-07-20: us-central1-f europe-west1-b asia-east1-c us-east1-c us-west1-b asia-northeast1-b asia-southeast1-b us-east4-c australia-southeast1-b europe-west2-b
  • 2017-07-21: us-central1-a us-central1-c europe-west1-d asia-east1-b us-east1-b us-east4-a us-west1-c australia-southeast1-c europe-west2-c asia-northeast1-c

• Container Engine now respects Kubernetes Pod Disruption Budgets, making stateful workloads more stable during upgrades. This also reduces disruptions during node auto-upgrades.

• gcloud container clusters get-credentials now correctly respects the HOMEDRIVE/HOMEPATH and USERPROFILE environment variables when generating the kubectl config file on Windows.

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

[CJ Cullen]

Known Issues with v1.7.1:

• GCP Internal Load Balancers created through Kubernetes services (a Beta feature in 1.7) have an issue that causes health-checks to fail preventing them from functioning. This will be fixed in a future patch release.

• Services of type=LoadBalancer in clusters that have nodes running Kubernetes v1.7 may fail GCP Load Balancer health checks. However, the Load Balancers will continue to forward traffic to backends. This issue will be fixed in future patch release and may require special upgrade actions.