[Google Cloud] Container Engine - Release Notes

[Kubernetes Engine - Release Notes]

[Google Cloud] Container Engine - Release Notes

---

January 8, 2020 Posted: 07 Jan 2020 04:00 PM PST Issue Do not update to version 1.16.0-gke.20 if you depend on HPA. Horizontal Pod Autoscaling is not working in this version due to a recently discovered issue. A fix will be released with GKE 1.16.3+.

January 7, 2020 Posted: 06 Jan 2020 04:00 PM PST Version updates GKE cluster versions have been updated as detailed in the following sections. See these instructions to get a full list of the Kubernetes versions you can run on your GKE masters and nodes, and to review the Rollout schedule. New default version The default version for new clusters is now 1.14.8-gke.12 (previously 1.13.11-gke.14). Scheduled automatic upgrades Masters and nodes with auto-upgrade enabled will be upgraded: Current version Upgrade version v1.12.x 1.13.12-gke.13 Rollouts are phased across multiple weeks, to ensure cluster and fleet stability. New versions available for upgrades and new clusters The following Kubernetes versions are now available for new clusters and for opt-in master upgrades and node upgrades for existing clusters. No channel v.1.13.x 1.13.12-gke.17 v.1.14.x 1.14.10-gke.0 v.1.15.x 1.15.7-gke.2 Stable channel and 1.13.x Stable channel There are no changes to the Stable channel this week. No channel 1.13.12-gke.17 Regular channel and 1.14.x Regular channel There are no changes to the Regular channel this week. No channel 1.14.10-gke.0 Rapid channel and 1.16.x Rapid channel There are no changes to the Rapid channel this week. Versions no longer available The following versions are no longer available for new clusters or upgrades. 1.12.10-gke.17 1.12.10-gke.20 1.12.10-gke.22 New features Feature You can now use Customer-managed encryption keys (beta) to control the encryption used for node boot disks as well as attached persistent disks in your clusters. Feature Consuming reservations in GKE is now generally available. Reservations allow you to reserve resources in a specific zone to ensure sufficient capacity is available for your workloads. Changes Changed New clusters and node-pools created with the GKE API will have node auto-upgrade enabled by default. This change ensures that your clusters have the most recent default Kubernetes version, bug fixes, and security patches. Existing scripts running against the gcloud CLI or integrating with the GKE API will follow this new default behavior. Node autoupgrades keep the nodes in your cluster up to date with the cluster master version when your master is updated on your behalf. To disable it explicitly, set autoUpgrade to false in the NodeManagement object.

You are subscribed to email updates from Kubernetes Engine - Release Notes. To stop receiving these emails, you may unsubscribe now.	Email delivery powered by Google
Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States